Hi, I was trying to install the latest Parrot. The latest source code is checked out from CVS. After configure, The make is stopping at ........ ops/core_ops.c ops/core_ops_prederef.c ops/core_ops_switch.c ops/core_ops_cg.c
Am I missing some thing?
Redhat Linux-9.0 perl, v5.8.4 built for i686-linux gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)
<al...@alfarrabio.di.uminho.pt> wrote: > 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.
>Hi, >I was trying to install the latest Parrot. The latest source code is >checked out from CVS. >After configure, The make is stopping at >........ >ops/core_ops.c >ops/core_ops_prederef.c >ops/core_ops_switch.c >ops/core_ops_cg.c
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
-----Original Message----- From: Dan Sugalski [mailto:d...@sidhe.org] Sent: Wednesday, October 27, 2004 6:19 PM To: Vijay D.; perl6-intern...@perl.org Subject: Re: Install-Problem
At 4:31 PM +0530 10/27/04, Vijay D. wrote: >Hi, >I was trying to install the latest Parrot. The latest source code is >checked out from CVS. >After configure, The make is stopping at >........ >ops/core_ops.c >ops/core_ops_prederef.c >ops/core_ops_switch.c >ops/core_ops_cg.c
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
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. :) -- Dan
--------------------------------------it's like this------------------- Dan Sugalski even samurai d...@sidhe.org have teddy bears and even teddy bears get drunk
> 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