linux-mips
[Top] [All Lists]

Re: Update for RedHat 7.1

To: Carsten Langgaard <carstenl@mips.com>
Subject: Re: Update for RedHat 7.1
From: Pete Popov <ppopov@pacbell.net>
Date: Wed, 12 Sep 2001 12:56:52 -0700
Cc: linux-mips@oss.sgi.com
References: <20010907230009.A1705@lucon.org> <3B9F21C9.985A1F0F@mips.com> <3B9F319B.E87DC64B@mips.com> <20010912094822.A4491@lucon.org> <3B9F9489.90608@pacbell.net> <3B9FBCB3.FDACFE3E@mips.com>
Sender: owner-linux-mips@oss.sgi.com
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3) Gecko/20010801
Carsten Langgaard wrote:
Pete Popov wrote:


H . J . Lu wrote:

On Wed, Sep 12, 2001 at 11:57:47AM +0200, Carsten Langgaard wrote:


Carsten Langgaard wrote:



I have installed your new set of RedHat7.1 RPMs, and tried to build Perl
natively.
But it fails with the following message:

`sh  cflags libperl.a toke.o`  toke.c
        CCCMD =  gcc -DPERL_CORE -c -fno-strict-aliasing
-I/usr/local/include
-O2

Cannot allocate 2676168 bytes after allocating 3899765696 bytes
make: *** [toke.o] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.43439 (%build)

RPM build errors:
  Bad exit status from /var/tmp/rpm-tmp.43439 (%build)



I tried to build perl again an now I get this message:

`sh  cflags libperl.a toke.o`  toke.c
        CCCMD =  gcc -DPERL_CORE -c -fno-strict-aliasing
-I/usr/local/include -O2
gcc: Internal error: Terminated (program cc1)
Please submit a full bug report.
See <URL:http://bugzilla.redhat.com/bugzilla/> for instructions.
make: *** [toke.o] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.53242 (%build)

RPM build errors:
  Bad exit status from /var/tmp/rpm-tmp.53242 (%build)



It may be a kernel/hardware bug. I have no problem building perl
natively.

Carsten, what board/cpu are you using?


On a Atlas board with a QED RM5261 CPU (little-endian).
The kernel is based on 2.4.3.

I would try the exact same userland and kernel version on a different board, preferably with a different cpu. Rebuild perl natively 10 times. If it works on the other board, there is a very good chance that this is a board or CPU problem. Native compiles seem to be very good for stressing the hardware.

Pete


<Prev in Thread] Current Thread [Next in Thread>