> Not stoping.. just compiling the computed-gotos C
> file. It take s alot
> of times, specially if you have a... old machine ;)
>
> There is some way to turn that off.
> Surelly someone will answer you soon with it :)
pass the --cgoto=0 flag to Configure.pl. I also have
RH 9.0 and would love someone to confirm that make
testj will fail on 3 tests (unless you additionally
pass it another flag). Interestingly enough - the
same failure ocurrs on Cygwin.
> Kind regards,
> Alberto
Cheers
Joshua Gatcomb
Limbic~Region
__________________________________
Do you Yahoo!?
Yahoo! Mail - You care about security. So do we.
http://promotions.yahoo.com/new_mail
Is it stopping, or just taking a long time? Those files take a while
to build, and a lot of memory to build in. Figure on a few minutes,
depending on your CPU, if you have enough memory. If the compiler
falls into swap (which'll happen if you've less than 256M or so) it
can take a half hour or more.
--
Dan
--------------------------------------it's like this-------------------
Dan Sugalski even samurai
d...@sidhe.org have teddy bears and even
teddy bears get drunk
xx.c
cc -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-I/usr/includ
e/gdbm -g -Dan_Sugalski -Larry -Wall -Wstrict-prototypes
-Wmissing-prototypes -W
inline -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings
-Waggre
gate-return -Winline -W -Wno-unused -Wsign-compare -Wformat-nonliteral
-Wformat-
security -Wpacked -Wdisabled-optimization -mno-accumulate-outgoing-args
-Wno-sha
dow -falign-functions=16 -I./include -I/usr/include -DHAS_JIT -DI386
-DHAVE_COMP
UTED_GOTO -I. -o xx.o -c xx.c
ops/core_ops_cg.c
cc1: Cannot allocate 56022680 bytes after allocating 116981760 bytes
gmake: *** [ops/core_ops_cg.o] Error 1
Regards,
V.
>I also have
>RH 9.0 and would love someone to confirm that make
>testj will fail on 3 tests (unless you additionally
>pass it another flag).
Here is the output for the fulltest on my redhat machine.
3 tests and 49 subtests skipped.
Failed 104/112 test scripts, 7.14% okay. 1851/1905 subtests failed,
2.83% okay.
make: *** [testg] Error 2
Regards,
Vijay.
If your really committed to using computed goto removing the -g may help.
Its gotten me past that kind of problem before.
--
It is our mission to synergistically negotiate mission-critical resources
so that we may conveniently foster parallel intellectual capital
You just ran out of memory during the build. (If this is a server
system you might want to check and make sure nothing else got killed
by the OOM monitor) The computed goto cores do make gcc more than a
little unhappy. Pass in the --cgoto=0 switch to configure, or throw
another half-gig or so of swap at your system. :)
> Failed 104/112 test scripts, 7.14% okay. 1851/1905 subtests failed,
> 2.83% okay.
> make: *** [testg] Error 2
Well, testing the now non-existing CGoto core with "make testg" is
probably not really helpfull ;)
> Regards,
> Vijay.
leo
> At 4:49 PM +0530 10/28/04, Vijay D. wrote:
>
>> I left the make for overnight :)
>> Here is the error I got..
>>
>> xx.c
>> ops/core_ops_cg.c
>>
>> cc1: Cannot allocate 56022680 bytes after allocating 116981760 bytes
>> gmake: *** [ops/core_ops_cg.o] Error 1
>
>
> You just ran out of memory during the build. (If this is a server
> system you might want to check and make sure nothing else got killed
> by the OOM monitor) The computed goto cores do make gcc more than a
> little unhappy. Pass in the --cgoto=0 switch to configure, or throw
> another half-gig or so of swap at your system. :)
In my experience early problems with core_ops_cg seem to have gone away
a few months back, which I assumed meant gcc now copes better with it.
It only takes 5 seconds on my 1.8GHz 256MB (no swap) laptop (and about
30MB memory?) with gcc 3.3.3
nickg@jenny ~/src/parrot $ rm ops/core_ops_cg.o
nickg@jenny ~/src/parrot $ time make ops/core_ops_cg.o
ops/core_ops_cg.c
real 0m4.564s
user 0m4.191s
sys 0m0.153s
To check that I've disabled ccache:
nickg@jenny ~/src/parrot $ which gcc
/usr/bin/gcc
Cheers,
Nick