From: Carsten Langgaard <carstenl@mips.com>
To: "H . J . Lu" <hjl@lucon.org>, linux-mips@oss.sgi.com
Subject: Re: Update for RedHat 7.1
Date: Wed, 12 Sep 2001 11:57:47 +0200 [thread overview]
Message-ID: <3B9F319B.E87DC64B@mips.com> (raw)
In-Reply-To: 3B9F21C9.985A1F0F@mips.com
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)
>
> I have build perl natively with your pervious set of RedHat7.1 RPMs,
> without any problems.
>
> /Carsten
>
> "H . J . Lu" wrote:
>
> > I updated a few packages, fixed a linker bug and rebuilt everything.
> >
> > H.J.
> > ----
> > My mini-port of RedHat 7.1 is at
> >
> > ftp://oss.sgi.com/pub/linux/mips/redhat/7.1/
> >
> > you should be able to put a small RedHat 7.1 on the mips/mipsel box and
> > compile the rest of RedHat 7.1 yourselves.
> >
> > Here are something you should know:
> >
> > 1. The cross compiler hosted on RedHat 7.1/ia32 is provided as a
> > toolchain rpm. The binary rpms for the mips and mipsel cross compilers
> > are included. You will need glibc 2.2.3-11 or above to use those
> > rpms. The glibc x86 binary rpms under RPMS/i386 should be ok.
> > 2. You have to find a way to put those rpms on your machine. I use
> > network boot and NFS root to do it.
> > 3. install.tar.bz2 has some scripts to prepare NFS root and install
> > RedHat 7.1 on a hard drive.
> > 4. baseline.tar.bz2 contains the cross build tree.
> >
> > Thanks.
> >
> > H.J.
>
> --
> _ _ ____ ___ 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
--
_ _ ____ ___ 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-12 9:58 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 [this message]
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
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=3B9F319B.E87DC64B@mips.com \
--to=carstenl@mips.com \
--cc=hjl@lucon.org \
--cc=linux-mips@oss.sgi.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox