From: Carsten Langgaard <carstenl@mips.com>
To: Pete Popov <ppopov@pacbell.net>
Cc: linux-mips@oss.sgi.com, "H . J . Lu" <hjl@lucon.org>
Subject: Re: Update for RedHat 7.1
Date: Thu, 13 Sep 2001 14:41:46 +0200 [thread overview]
Message-ID: <3BA0A98A.75DA372@mips.com> (raw)
In-Reply-To: 3B9FBE04.3010304@pacbell.net
Pete Popov wrote:
> 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.
>
Ok, I found the problem, it turn out that I only had 128K swap space, it should
have been 128M.
So after increasing my swap space, I was able to compile perl.
Thanks a lot.
/Carsten
>
> Pete
--
_ _ ____ ___ Carsten Langgaard Mailto:carstenl@mips.com
|\ /|||___)(___ MIPS Denmark Direct: +45 4486 5527
| \/ ||| ____) Lautrupvang 4B Switch: +45 4486 5555
TECHNOLOGIES 2750 Ballerup Fax...: +45 4486 5556
Denmark http://www.mips.com
next prev parent reply other threads:[~2001-09-13 12:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-08 6:00 Update for RedHat 7.1 H . J . Lu
2001-09-12 8:50 ` Carsten Langgaard
2001-09-12 9:57 ` Carsten Langgaard
2001-09-12 16:48 ` H . J . Lu
2001-09-12 16:59 ` Pete Popov
2001-09-12 19:51 ` Carsten Langgaard
2001-09-12 19:56 ` Pete Popov
2001-09-12 23:28 ` Ralf Baechle
2001-09-13 12:41 ` Carsten Langgaard [this message]
2001-09-13 15:06 ` Carsten Langgaard
2001-09-13 15:14 ` H . J . Lu
2001-09-14 7:52 ` Carsten Langgaard
2001-09-14 15:24 ` H . J . Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3BA0A98A.75DA372@mips.com \
--to=carstenl@mips.com \
--cc=hjl@lucon.org \
--cc=linux-mips@oss.sgi.com \
--cc=ppopov@pacbell.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.