From: "H. J. Lu" <hjl@lucon.org>
To: Lyle Bainbridge <lyle@zevion.com>
Cc: linux-mips@linux-mips.org
Subject: Re: GCC 3.2 to build mips-linux kernel
Date: Fri, 11 Oct 2002 10:53:32 -0700 [thread overview]
Message-ID: <20021011105332.A11498@lucon.org> (raw)
In-Reply-To: <NCBBKGDBOEEBDOELAFOFAEPMDAAA.lyle@zevion.com>; from lyle@zevion.com on Fri, Oct 11, 2002 at 12:34:53PM -0500
On Fri, Oct 11, 2002 at 12:34:53PM -0500, Lyle Bainbridge wrote:
>
> I built a mips-linix 2.4.18 kernel for an AU1500 board using:
> gcc-3.2 / binutils-2.13 / glibc-2.2.5
^^^^^^^^^^^^^^^
Bad choice.
>
> It builds and executes but is unsuccessful during startup.
> I have attached the log at the end of this message. It
> appears to have skipped a number of steps. I noticed that
> a working kernel built with gcc 2.95.3 is 800K larger.
> (~3MB versus !2.2MB).
>
> I'm a little confused, and wondered if the 3.2 compiler requires
> some patching to work for mips-linux.
>
gcc 3.2 I released for Linux/mips builds 2.4.20-pre6 kernel for malta
just fine. But you are strongly recommended to use my latest Linux
binutils.
H.J.
prev parent reply other threads:[~2002-10-11 17:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-11 17:34 GCC 3.2 to build mips-linux kernel Lyle Bainbridge
2002-10-11 17:34 ` Lyle Bainbridge
2002-10-11 17:53 ` H. J. Lu [this message]
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=20021011105332.A11498@lucon.org \
--to=hjl@lucon.org \
--cc=linux-mips@linux-mips.org \
--cc=lyle@zevion.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