From: Ralf Baechle <ralf@linux-mips.org>
To: Lyle Bainbridge <lyle@zevion.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: Mips cross toolchain
Date: Tue, 20 Aug 2002 18:02:23 +0200 [thread overview]
Message-ID: <20020820180223.A24985@linux-mips.org> (raw)
In-Reply-To: <NCBBKGDBOEEBDOELAFOFKEGGCPAA.lyle@zevion.com>; from lyle@zevion.com on Tue, Aug 20, 2002 at 10:58:13AM -0500
On Tue, Aug 20, 2002 at 10:58:13AM -0500, Lyle Bainbridge wrote:
> I'm a linux kernel newbie, and this is my first linux-mips posting.
> I have built a big endian, elf, cross toolchain for mips32 (I'm using
> an Alchemy Au1500 SOC) based on the GCC 3.0.4, Binutils 2.11.2 and
> Newlib 1.9.0. My intention is to now use it to compile the 2.4.19 kernel.
>
> I am still figuring out how to cross compile the kernel, but I was
> wondering if I had used the correct versions of GCC and Binutils to
> succesfully build a stable kernel. Also, are there any patches I would
> need? So far I've used the stock distributions from gnu.org.
>
> Any advice would be most appreciated.
Looks like you installed the toolchain in a different directory that
it was built for.
Ralf
next prev parent reply other threads:[~2002-08-20 16:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-20 15:58 Mips cross toolchain Lyle Bainbridge
2002-08-20 15:54 ` Pete Popov
2002-08-20 15:58 ` Lyle Bainbridge
2002-08-20 16:02 ` Ralf Baechle [this message]
2002-08-20 16:05 ` Daniel Jacobowitz
2002-08-20 16:29 ` Joe George
2002-08-20 16:57 ` Pete Popov
2002-08-20 17:22 ` Joe George
2002-08-20 17:41 ` Pete Popov
2002-08-20 18:47 ` Lyle Bainbridge
2002-08-20 18:47 ` Lyle Bainbridge
2002-08-20 19:04 ` Pete Popov
-- strict thread matches above, loose matches on Subject: below --
2002-09-18 20:08 Mips Cross Toolchain Lyle Bainbridge
2002-09-18 20:08 ` Lyle Bainbridge
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=20020820180223.A24985@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@oss.sgi.com \
--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