Hi
It continues....
and sometime later dies....
I got another interesting error message... "virtual memory exhausted"=20
using a non-root account....
Flaky RAM ?


mandag 8. sep 2003 kl. 11:57 skrev Manuel Bouyer:

> On Mon, Sep 08, 2003 at 08:25:06AM +0200, Niels S. Eliasen wrote:
>> Yes...that might be an idea....
>> Some additional info..this is the latest error-message when trying to
>> compile perl:
>>
>> =3D=3D=3D> Building for perl-5.6.1nb9
>> `sh  cflags libperl.so miniperlmain.o` -DPIC -fPIC miniperlmain.c
>>           CCCMD =3D  cc -DPERL_CORE -c -fno-strict-aliasing
>> -I/usr/pkg/include -O2 -I/usr/pkg/include
>> `sh  cflags libperl.so perl.o` -DPIC -fPIC perl.c
>>           CCCMD =3D  cc -DPERL_CORE -c -fno-strict-aliasing
>> -I/usr/pkg/include -O2 -I/usr/pkg/include
>> `sh  cflags libperl.so gv.o` -DPIC -fPIC gv.c
>>           CCCMD =3D  cc -DPERL_CORE -c -fno-strict-aliasing
>> -I/usr/pkg/include -O2 -I/usr/pkg/include
>> `sh  cflags libperl.so toke.o` -DPIC -fPIC toke.c
>>           CCCMD =3D  cc -DPERL_CORE -c -fno-strict-aliasing
>> -I/usr/pkg/include -O2 -I/usr/pkg/include
>> cc: Internal compiler error: program cc1 got fatal signal 11
>> *** Error code 1
>>
>> Stop.
>> make: stopped in /usr/pkgsrc/lang/perl5/work/perl-5.6.1
>> *** Error code 1
>
> If you restart the build, does it stop at the same place, or does it=20=

> compile
> this file and die later ?
> If so, it's most probably a hardware issue, bad RAM or something like=20=

> that
> (or maybe a broken CPU fan).
>
> --
> Manuel Bouyer, LIP6, Universite Paris VI.          =20
> Manuel.Bouyer@lip6.fr
>      NetBSD: 24 ans d'experience feront toujours la difference
> --
>
>
mvh/kind regards
Niels S. Eliasen
H=F8rhavevej 1
DK-4250, Fuglebjerg
Tel/Cell: +45 46 32 85 27 +45 21 77 95 90
mailto:Niels.Eliasen@delfi-konsult.com