Rakudo's --gen-parrot option for Configure.pl defaults to invoking Parrot's
Configure.pl with --optimize. In turn, that flag is documented as adding
the Perl 5 configuration value $Config{optimize} to the C compiler flags.
This is sane.
However, I can't find a way to *not* build with optimisation
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #61208]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=61208 >
Hello,
with Fedora 10 the place for building RPMs change from /usr/src/redhat
to t
On Sat, 25 Oct 2008, Michael P. Soulier wrote:
> On 15/10/08 Andy Dougherty said:
>
> > > No file by that name on the box anywhere.
> >
> > Are you *sure*? I don't know exactly what name you searched for, nor how
> > you searched for it, but this is just the sort of error message I'd expect
> >
On 15/10/08 Andy Dougherty said:
> > No file by that name on the box anywhere.
>
> Are you *sure*? I don't know exactly what name you searched for, nor how
> you searched for it, but this is just the sort of error message I'd expect
> to see if you did have an old libparrot.so somewhere else on
[reforwarding this so it gets in the bug-tracking system]
On Wed, 15 Oct 2008, Michael P. Soulier wrote:
> I'm trying to build parrot on a CentOS 4.6 box and it's failing at link time.
>
> gcc -o miniparrot src/main.o src/null_config.o \
> -Wl,-rpath=/home/msoulier/downloads/parrot-0.7.1/blib/l
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #59918]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=59918 >
On Wed, Oct 15, 2008 at 9:52 AM, Will Coleda <[EMAIL PROTECTED]> wrote:
> Do you ha
On Wed, 15 Oct 2008, Michael P. Soulier wrote:
> I'm trying to build parrot on a CentOS 4.6 box and it's failing at link time.
>
> gcc -o miniparrot src/main.o src/null_config.o \
> -Wl,-rpath=/home/msoulier/downloads/parrot-0.7.1/blib/lib
> -L/home/msoulier/downloads/parrot-0.7.1/blib/lib -lpar
On Wed, Oct 15, 2008 at 11:04 AM, Andy Dougherty <[EMAIL PROTECTED]> wrote:
> Do you have a link for that bug report? I vaguely recall something like
> that where the tcsh was a red herring -- it was really an environment
> variable setting -- but I don't recall any more details offhand.
http://m
On Wed, Oct 15, 2008 at 9:52 AM, Will Coleda <[EMAIL PROTECTED]> wrote:
> Do you have a previously installed parrot? It's possible that we're
> inadvertently linking against the installed libparrot instead of the
> one in your build dir.
No file by that name on the box anywhere.
Mike
--
Michael
On Wed, 15 Oct 2008, Michael P. Soulier wrote:
> Hello,
>
> I'd report a bug but this link
>
> http://www.parrot.org/docs/submissions.html
>
> is broken.
>
> I'm trying to build parrot on a CentOS 4.6 box and it's failing at link time.
>
> gcc -o miniparrot src/main.o src/null_config.o \
> -W
# New Ticket Created by Will Coleda
# Please include the string: [perl #59914]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=59914 >
On Wed, Oct 15, 2008 at 9:43 AM, Michael P. Soulier
<[EMAIL PROTECTED]> wrote:
> Hello,
>
On Wed, Oct 15, 2008 at 9:43 AM, Michael P. Soulier
<[EMAIL PROTECTED]> wrote:
> Hello,
>
> I'd report a bug but this link
>
> http://www.parrot.org/docs/submissions.html
>
> is broken.
Whoops. We're in the middle of migrated to that site:
http://www.parrotcode.org/docs/submissions.html has the in
Hello,
I'd report a bug but this link
http://www.parrot.org/docs/submissions.html
is broken.
I'm trying to build parrot on a CentOS 4.6 box and it's failing at link time.
gcc -o miniparrot src/main.o src/null_config.o \
-Wl,-rpath=/home/msoulier/downloads/parrot-0.7.1/blib/lib
-L/home/msoulier
On Friday 10 October 2008 14:52:54 Gabor Szabo wrote:
Hi Gabor,
> Now at r31867 I get the following.
> This PASS-es but there seem to be an error somewhere anyway.
> [EMAIL PROTECTED]:~/work/parrot/ext/Parrot-Embed$ ./Build test
> t/00-loadok
> t/interp.1/26 Parrot VM: Can't stat no file
On Sunday 28 September 2008 05:47:14 Nikolay Ananiev wrote:
> I'm trying to build parrot r31477 with visual studio 2008 on vista home and
> i get the following error
>
> src\pmc\exceptionhandler.c
> .\src\pmc\exceptionhandler.pmc(34) : error C2275:
> 'Parrot_ExceptionHandler_attri
> butes' : illeg
I'm trying to build parrot r31477 with visual studio 2008 on vista home and
i get the following error
src\pmc\exceptionhandler.c
.\src\pmc\exceptionhandler.pmc(34) : error C2275:
'Parrot_ExceptionHandler_attri
butes' : illegal use of this type as an expression
d:\dev\projects_out\parrot
NotFound wrote:
> On Wed, Sep 10, 2008 at 8:12 PM, chromatic <[EMAIL PROTECTED]> wrote:
>
>> The line numbers reported by clang seem sensible enough, but do they match
>> values in src/pmc/default.str? Mine contains:
>>
>> #define _CONST_STRING_45 80
>> #define _CONST_STRING_103 534
>> #define _C
Moritz Lenz wrote:
I tried to build parrot with the clang, an llvm frontend. It provides a
script called 'ccc', which accepts the same options as gcc.
Configure works fine (perl Configure.pl --verbose --cc=ccc --link=ccc).
Works for me with "perl Configure.pl --cc=llvm-gcc --link=llvm-gcc".
Vasily Chekalkin wrote:
> Moritz Lenz wrote:
>> I tried to build parrot with the clang, an llvm frontend. It provides a
>> script called 'ccc', which accepts the same options as gcc.
>
> Works for me with "perl Configure.pl --cc=llvm-gcc --link=llvm-gcc".
That works for me too, but it's a complet
On Wed, Sep 10, 2008 at 8:12 PM, chromatic <[EMAIL PROTECTED]> wrote:
> The line numbers reported by clang seem sensible enough, but do they match
> values in src/pmc/default.str? Mine contains:
>
> #define _CONST_STRING_45 80
> #define _CONST_STRING_103 534
> #define _CONST_STRING_144 _CONST_STR
On Wednesday 10 September 2008 11:07:41 Moritz Lenz wrote:
> That doesn't the seem to be case here. I tried with a small sample
> script that include a .str file, and it works fine.
>
> A
> ack -a '_CONST_STRING_65\b'
>
> didn't find anything; so is this a broken macro expansion somewhere?
The li
chromatic wrote:
> On Wednesday 10 September 2008 10:45:12 Moritz Lenz wrote:
>
>> I tried to build parrot with the clang, an llvm frontend. It provides a
>> script called 'ccc', which accepts the same options as gcc.
>>
>> Configure works fine (perl Configure.pl --verbose --cc=ccc --link=ccc).
>>
On Wednesday 10 September 2008 10:45:12 Moritz Lenz wrote:
> I tried to build parrot with the clang, an llvm frontend. It provides a
> script called 'ccc', which accepts the same options as gcc.
>
> Configure works fine (perl Configure.pl --verbose --cc=ccc --link=ccc).
>
> src/pmc/default.c:65:36
I tried to build parrot with the clang, an llvm frontend. It provides a
script called 'ccc', which accepts the same options as gcc.
Configure works fine (perl Configure.pl --verbose --cc=ccc --link=ccc).
The build starts fine, but fails while compiling the first pmc:
clang -emit-llvm-bc -x c -o
Keeping fingers crossed, I'm marking this ticket resolved.
Another vote of confidence for arch-config-patch_v2.txt.
During the YAPC Parrot Workshop, Jeff Bisbee encountered the problem.
core_ops.c fails to compile, giving a "no such instruction: 'trap'" error.
Applying the patch resolved the problem.
Config: Darwin PPC 1.5.3 with new XCode that updated
On Sun May 25 13:15:10 2008, tetragon wrote:
> And here's a newer version of the patch that I use. This one changes
> config/init/hints/darwin.pm instead of config/init/defaults.pm
Patch applied to trunk in r28513. Thanks to tetragon, testers who have
posted so far, and participants in Parrot/R
... which leaves:
> > Mac OS X 10.5 on intel
>
Can anyone give tetragon's patch a whirl on one on those shiny
ultra-thin new Macs? If it works, we'll apply to trunk.
Thank you very much.
On Sun May 25 13:15:10 2008, tetragon wrote:
> And here's a newer version of the patch that I use. This one changes
> config/init/hints/darwin.pm instead of config/init/defaults.pm
This worked for me on Mac OS X 10.4 on ppc.
Given what we've experienced, I'd like to verify that it also works on
This is the patch that I'm currently using to get Configure.pl to ignore
-arch flags in the Perl 5 config on Darwin.
Index: config/init/defaults.pm
===
--- config/init/defaults.pm (revision 26775)
+++ config/init/defaults.pm (w
# New Ticket Created by James Keenan
# Please include the string: [perl #52214]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=52214 >
This is one of a series of tickets reporting issues encountered at a
Parrot/Rakudo build
# New Ticket Created by Will Coleda
# Please include the string: [perl #43981]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43981 >
... with Xcode.
22:09 <@Coke> http://www.coleda.com/tmp/parrot.xcodeproj.tar.gz -
down
chromatic wrote:
On Sunday 01 April 2007 07:15, Ron Blaschke wrote:
As recently discussed it is currently necessary to include the absolute
path to F in the environment variable PATH. This should be
done before trying to built parrot, otherwise one gets a broken
F and F. One
needs a "make cle
Steve Peters wrote:
On Sun, Apr 01, 2007 at 04:15:24PM +0200, Ron Blaschke wrote:
As recently discussed it is currently necessary to include the absolute
path to F in the environment variable PATH. This should be
done before trying to built parrot, otherwise one gets a broken
F and F. One
n
Eric Hanchrow wrote:
"Ron" == Ron Blaschke <[EMAIL PROTECTED]> writes:
Ron> If you see this error
...
Ron> the file has Windows line endings
Dare I suggest that parrot not be so fussy about line endings?
I second that. ;) Actually, both things are supposed only as
workarounds until
On Sunday 01 April 2007 07:15, Ron Blaschke wrote:
> As recently discussed it is currently necessary to include the absolute
> path to F in the environment variable PATH. This should be
> done before trying to built parrot, otherwise one gets a broken
> F and F. One
> needs a "make clean" or rem
On Sun, Apr 01, 2007 at 04:15:24PM +0200, Ron Blaschke wrote:
> Hi,
>
> As recently discussed it is currently necessary to include the absolute
> path to F in the environment variable PATH. This should be
> done before trying to built parrot, otherwise one gets a broken
> F and F. One
> need
> "Ron" == Ron Blaschke <[EMAIL PROTECTED]> writes:
Ron> If you see this error
...
Ron> the file has Windows line endings
Dare I suggest that parrot not be so fussy about line endings?
--
If you're trying to choose between two theories and one gives
you an excuse for being lazy, the
Hi,
As recently discussed it is currently necessary to include the absolute
path to F in the environment variable PATH. This should be
done before trying to built parrot, otherwise one gets a broken
F and F. One
needs a "make clean" or remove *both* files before trying again. Make
sure to
chromatic wrote:
> On Saturday 23 December 2006 11:32, Ron Blaschke wrote:
>
>> It would be great if you could make the change right away. I thought it
>> was just too small of a change to submit an official patch.
>
> Thanks, applied as of r16229.
>
>>> This is generally only tricky when build
On Saturday 23 December 2006 11:32, Ron Blaschke wrote:
> It would be great if you could make the change right away. I thought it
> was just too small of a change to submit an official patch.
Thanks, applied as of r16229.
> > This is generally only tricky when building in-tree, as there's no
>
chromatic wrote:
> On Friday 22 December 2006 12:54, Ron Blaschke wrote:
>>
>> -void Parrot_register_pmc(Parrot_INTERP, Parrot_PMC);
>> -void Parrot_unregister_pmc(Parrot_INTERP, Parrot_PMC);
>> +PARROT_API void Parrot_register_pmc(Parrot_INTERP, Parrot_PMC);
>> +PARROT_API void Parrot_unregis
On Friday 22 December 2006 12:54, Ron Blaschke wrote:
> The necessary change is:
>
>
> $ svn diff include/parrot/extend.h
> Index: include/parrot/extend.h
> ===
> --- include/parrot/extend.h (revision 16218)
> +++ include/par
chromatic wrote:
> On Friday 22 December 2006 11:08, Ron Blaschke wrote:
>> There are three steps necessary (four using VC8).
>>
>> 1) Two additional functions need to be exported.
>> Parrot_register_pmc
>> Parrot_unregister_pmc
>
> In some .def file somewhere, or marked somehow in the so
On Friday 22 December 2006 11:08, Ron Blaschke wrote:
> I have managed to build Parrot::Embed on Windows/VC8, and judging from
> the test output it works. There are two warnings, but I guess those are
> no problem?
>
> $ ./Build test
> t\interpok 1/31Parrot VM: Can't stat no file here
I have managed to build Parrot::Embed on Windows/VC8, and judging from
the test output it works. There are two warnings, but I guess those are
no problem?
$ ./Build test
t\interpok 1/31Parrot VM: Can't stat no file here, code 2.
error:imcc:syntax error, unexpected IDENTIFIER
On 2/20/06, Joshua Hoblitt <[EMAIL PROTECTED]> wrote:
> > Yes, /usr/local/lib is already in /etc/ld.so.conf.
>
> Perhaps you need to run `ldconfig` as root.
Yep - that takes care of it.
Cheers,
Rob
On 2/20/06, Joshua Hoblitt <[EMAIL PROTECTED]> wrote:
> On Tue, Feb 21, 2006 at 10:06:36AM +1100, Sisyphus wrote:
> > Yes, /usr/local/lib is already in /etc/ld.so.conf.
>
> Perhaps you need to run `ldconfig` as root.
>
> > $LD_LIBRARY_PATH is initially empty. If I don't add '/usr/local/lib' to it,
On Tue, Feb 21, 2006 at 10:06:36AM +1100, Sisyphus wrote:
> Yes, /usr/local/lib is already in /etc/ld.so.conf.
Perhaps you need to run `ldconfig` as root.
> $LD_LIBRARY_PATH is initially empty. If I don't add '/usr/local/lib' to it,
> then when I run 'parrot hello.pir', I get (transcribed):
>
>
- Original Message -
From: "Nick Glencross" <[EMAIL PROTECTED]>
To: "Sisyphus" <[EMAIL PROTECTED]>; "Perl 6 Internals"
Sent: Monday, February 20, 2006 9:47 PM
Subject: Re: Building parrot-0.4.1 on Win32
> On 2/20/06, Sisyphus <[EMAIL
On 2/20/06, Sisyphus <[EMAIL PROTECTED]> wrote:
> Oh one other thing on Linux I had to add (the standard location)
> /usr/local/lib to LD_LIBRARY_PATH. I've not had to do that before ... and
> the README suggests that I shouldn't have to do it wrt parrot. It says:
>
> "But please note th
- Original Message -
From: "Jonathan Worthington"
.
.
> So
> I guess one answer is to try the latest Parrot, either from SVN or by
> downloading a snapshot:
> http://svn.perl.org/snapshots/parrot/
>
Thanks for the reply, Jonathan. A few things came up and I've not been able
to get back u
"Sisyphus" <[EMAIL PROTECTED]> wrote:
My first post here. First up, is there a better place to ask questions
relating to the building of parrot ? If so ... where ? If not ... read
on.
Welcome to the list and yes, you're in the right place. :-)
I'm on Windows 2000, and parrot-0.4.1 builds
Hi,
My first post here. First up, is there a better place to ask questions
relating to the building of parrot ? If so ... where ? If not ... read on.
I'm on Windows 2000, and parrot-0.4.1 builds straight out of the box using
MSVC++ 7.0 (.NET) and nmake. But there's a couple of issues when using
At 12:19 10/06/2005 +0200, you wrote:
On Saturday 04 June 2005 20:29, Clement Cherlin wrote:
> I include a patch I made for the above problems. Some of the changes are
> kind of kludgey, so I would appreciate comments and suggestions on how to
> improve them.
Thanks, applied.
Please, revert thi
Nick Glencross wrote:
> My understand is that on Windows DLLs must be self-contained and cannot
> have unreferenced symbols, and so I've linked against libparrot.so which
> of course pulls in much of its code. I see this also being done in the
> MSWin32 case...
Yes, Windows needs to know where the
Matt Diephouse wrote:
Nick Glencross <[EMAIL PROTECTED]> wrote:
+# Here comes some stuff for Cygwin
+if ($^O eq 'cygwin') {
+$LD_LOAD_FLAGS .= ' ../src/parrot_config.o';
+$LIBPARROT = qq[-L../blib/lib -lparrot];
+}
Make sure this patch will work to make Tcl too (languages/tcl/), whi
Nick Glencross <[EMAIL PROTECTED]> wrote:
> +# Here comes some stuff for Cygwin
> +if ($^O eq 'cygwin') {
> +$LD_LOAD_FLAGS .= ' ../src/parrot_config.o';
> +$LIBPARROT = qq[-L../blib/lib -lparrot];
> +}
Make sure this patch will work to make Tcl too (languages/tcl/), which
has PMCs inside
Nick Glencross wrote:
My understand is that on Windows DLLs must be self-contained and cannot
have unreferenced symbols, and so I've linked against libparrot.so which
of course pulls in much of its code. I see this also being done in the
MSWin32 case...
Sorry, I typed libparrot.so when what
Clement Cherlin wrote:
I still haven't gotten compilation to finish, but it's a lot further
along than when I started. Currently, it fails with a zillion "undefined
reference" errors on the command
g++ -s -g -shared "C:/Users/Clement/src/parrot/parrot/src/extend.o"
-o python_group.dll "lib-p
On Saturday 04 June 2005 20:29, Clement Cherlin wrote:
> I include a patch I made for the above problems. Some of the changes are
> kind of kludgey, so I would appreciate comments and suggestions on how to
> improve them.
Thanks, applied.
jens
On Tue, 7 Jun 2005, [iso-8859-1] François PERRAD wrote:
> I work with MinGW, ActivePerl & cmd.exe.
> I introduced the configuration variable slash_exec.
> On all platform 'slash' == 'slash_exec'
> except with MinGW where :
> slash => '/' (need by mingw32-make)
> 'slash_exec' => '
At 11:29 04/06/2005 -0700, you wrote:
I actually have Linux installed on this machine, but for reasons which
I'm not going to get into here I use Win98 for day-to-day computing. I
therefore took it as a challenge to get Parrot to build with crufty ol'
command.com.
I used MinGW 3.1.0-1 and Active
On Saturday 04 June 2005 20:29, Clement Cherlin wrote:
> I actually have Linux installed on this machine, but for reasons which
> I'm not going to get into here I use Win98 for day-to-day computing. I
> therefore took it as a challenge to get Parrot to build with crufty ol'
> command.com.
I have a
I actually have Linux installed on this machine, but for reasons which
I'm not going to get into here I use Win98 for day-to-day computing. I
therefore took it as a challenge to get Parrot to build with crufty ol'
command.com.
I used MinGW 3.1.0-1 and ActivePerl 5.8.6.811 to build Parrot.
I conf
Matt Diephouse wrote:
> Oops. I forgot to mention that some recent (big) changes to Parrot has
> been causing my Forth implementation some trouble. I filed a bug
> report earlier today; hopefully it'll get fixed soon (generally
> doesn't take long).
No problem ... my interest is tangential at the
On Mon, 08 Nov 2004 18:41:50 -0700, Jack J. Woehr <[EMAIL PROTECTED]> wrote:
> Matt Diephouse wrote:
> > Enjoy (Parrot). :-)
>
> I did ... briefly!
[ . . . ]
> > Segmentation Fault (core dumped)
Oops. I forgot to mention that some recent (big) changes to Parrot has
been causing my Forth im
Matt Diephouse wrote:
> Enjoy (Parrot). :-)
I did ... briefly!
[17:33:55 [EMAIL PROTECTED]:/usr/local/src/PerlSource/parrot_stuff/forth]$
parrot forth.pir
Parrot Forth 0.1
Type `bye` to exit
> words
over 2* spaces */ swap 2dup rot drop depth cr 0sp - space words / emit
At 10:29 PM -0700 11/7/04, Jack J. Woehr wrote:
Nicholas Clark wrote:
So I think that deleting the empty directory /usr/local/uplevel for the
duration of the build should solve your problem.
Removed the dir, finished the build, recreated the dir, and make
install worked.
Now on to actually *try
On Sun, 07 Nov 2004 22:29:46 -0700, Jack J. Woehr <[EMAIL PROTECTED]> wrote:
> Now on to actually *trying out* Parrot ... as a former ANSForth Technical
> Committee
> member, think I'll try the Forth first :-)
Hurm. The Forth in CVS has been somewhat abandoned (though
functional). I've been worki
On Nov 7, 2004, at 12:10 PM, Leopold Toetsch wrote:
Jack J. Woehr <[EMAIL PROTECTED]> wrote:
Okay, I now configured
perl Configure.pl --prefix=/usr/local/uplevel --cc=gcc --cxx=gcc
--icuplatform=sparc-sun-solaris2.9
The build bombs in:
string_set_data_directory: ICU data files not fou
Jack J. Woehr <[EMAIL PROTECTED]> wrote:
> Okay, I now configured
> perl Configure.pl --prefix=/usr/local/uplevel --cc=gcc --cxx=gcc
> --icuplatform=sparc-sun-solaris2.9
> The build bombs in:
> string_set_data_directory: ICU data files not found(apparently) for
> directory [/usr/loca
Nicholas Clark wrote:
> So I think that deleting the empty directory /usr/local/uplevel for the
> duration of the build should solve your problem.
Removed the dir, finished the build, recreated the dir, and make install worked.
Now on to actually *trying out* Parrot ... as a former ANSForth Tech
On Sun, Nov 07, 2004 at 02:57:04PM -0800, Jeff Clites wrote:
> On Nov 7, 2004, at 3:20 PM, Jack J. Woehr wrote:
>
> >Nicholas Clark wrote:
> >
> >>On Sun, Nov 07, 2004 at 01:17:28PM -0700, Jack J. Woehr wrote:
> >>>Okay, I now configured
> >>>
> >>> perl Configure.pl --prefix=/usr/local/upleve
On Nov 7, 2004, at 3:20 PM, Jack J. Woehr wrote:
Nicholas Clark wrote:
On Sun, Nov 07, 2004 at 01:17:28PM -0700, Jack J. Woehr wrote:
Okay, I now configured
perl Configure.pl --prefix=/usr/local/uplevel --cc=gcc
--cxx=gcc --icuplatform=sparc-sun-solaris2.9
The build bombs in:
string_set
Nicholas Clark wrote:
> On Sun, Nov 07, 2004 at 01:17:28PM -0700, Jack J. Woehr wrote:
> > Okay, I now configured
> >
> > perl Configure.pl --prefix=/usr/local/uplevel --cc=gcc --cxx=gcc
> > --icuplatform=sparc-sun-solaris2.9
> >
> > The build bombs in:
> >
> > string_set_data_directory
On Sun, Nov 07, 2004 at 01:17:28PM -0700, Jack J. Woehr wrote:
> Okay, I now configured
>
> perl Configure.pl --prefix=/usr/local/uplevel --cc=gcc --cxx=gcc
> --icuplatform=sparc-sun-solaris2.9
>
> The build bombs in:
>
> string_set_data_directory: ICU data files not found(apparently)
Okay, I now configured
perl Configure.pl --prefix=/usr/local/uplevel --cc=gcc --cxx=gcc
--icuplatform=sparc-sun-solaris2.9
The build bombs in:
string_set_data_directory: ICU data files not found(apparently) for
directory [/usr/local/uplevel/blib/lib/icu/2.6.1]make: ***
[runtime/parr
"Gregor N. Purdy" wrote:
> On that last call to nmake, if you get dropped back into Configure.pl,
> something is wrong configure-wise.
I did a fresh CVS checkout just now, and nmake calls Configure.pl
again.
--
Sebastian Bergmann
http://sebastian-bergmann.de/ http://phpO
Sebastian --
I noticed on your first post of the nmake run log that you ended up
re-running Configure.pl. That's not a good sign. I don't know what
time you grabbed code from CVS, but if you wouldn't mind doing the
following to be *very* sure you've got all the latest checkins, I'd
appreciate it.
Dan Sugalski wrote:
> Argh! Platform quoting issues. Can you edit Makefile and change the
> appropriate ' to " and see how things go from there?
Okay, it now proceeds further than before, but now it gets stuck at
test_main.c
../include\parrot/parrot.h(76): fatal error C1083:
include file canno
At 09:42 PM 12/30/2001 +0100, Sebastian Bergmann wrote:
>'lo there,
>
> just tried to build Parrot 0.3 (from CVS) on Win32 -- but I didn't
> succeed.
Argh! Platform quoting issues. Can you edit Makefile and change the
appropriate ' to " and see how things go from there?
'lo there,
just tried to build Parrot 0.3 (from CVS) on Win32 -- but I didn't
succeed.
The output of
perl Configure.pl
can be found at
http://www.sebastian-bergmann.de/parrot_configure.txt
and the output of
nmake
can be found at
http://www.sebastian-bergmann.
Jason Diamond:
# > # Once I got past that, it couldn't link to
# classes/intclass.obj. After
# > # looking at the output a bit, I found out that intclass.obj is
# > # being written
# > # to the main parrot directory and not into the classes
# > # directory. The option
# > # for CL to specify the o
Brent (and Jason) --
Based on Dan's agreement to the approach, I just checked in the starting
point files for doing this "right". Please have a look and send patches
against those files. As soon as we get config wired up to autoselect the
appropriate platform files, we'll be able to make this All
Dan --
> platform.c and platform.h is exactly what we're going to do. We need a
> platforms directory as well. In there we'll have a win32.[ch], a
> linux.[ch], a vms.[ch], a generic.[ch] and so on. Configure.pl will copy
> the appropriate ones up and rename them platform.c & platform.h, and we'
On Thu, 1 Nov 2001, Gregor N. Purdy wrote:
> We may end up needing to consolidate these platform-isms into a small
> number of files (one?) rather than have them split by type (like I did for
> Parrot_*_time). I don't know if we can get away with something as simple
> as platform.[hc] with all th
Hi.
> in /usr/include/sys/stat.h. As for what to includ in Windows to get
> these (if anything), or what should be done to get them, I'm unsure.
> I suppose for now, you could paste the above into a header file
> somewhere with a #ifdef WIN32 around it to get things compiling.
I'd suspect that
Brent --
[ snip Jason Diamond's question ]
> No, this seems to be a case of Unix-centrism. (I feel your pain--I'm on
> Win32 too.) I'm CCing perl6-internals on this, since I don't really
> have the C experience to know what to do here.
I just posted a reply to someone else on the matter. If
Jason --
> I'm trying to build parrot on my Windows 2000 box and am failing when
> compiling core_ops.c with these errors:
>
> core_ops.c(370) : error C2065: 'S_IRUSR' : undeclared identifier
> core_ops.c(370) : error C2065: 'S_IWUSR' : undeclared identifier
> core_ops.c(370) : error C2065: 'S_
Jason Diamond:
# > Can you give me the output of that time.c compilation? Someone just
# > asked for feedback on how that was working.
#
# It was complaining about SYSTEMTIME not being defined. You
# have to #include
# for that. But that caused a redefinition error
# for BOOL. So I
# renamed the
Jason Diamond:
# I'm having trouble building the latest parrot sources from
# CVS on Windows
# 2000. The Configure.pl script ran fine but after running
# nmake test_prog.exe
# I'm getting an error while compiling core_ops.c:
#
# core_ops.c(370) : error C2065: 'S_IRUSR' : undeclared identifier
# co
92 matches
Mail list logo
