From: Johannes Stezenbach <js@convergence.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jan-Benedict Glaw <jbglaw@lug-owl.de>,
SGI MIPS list <linux-mips@oss.sgi.com>
Subject: Re: Toolchain question
Date: Mon, 18 Mar 2002 17:02:28 +0100 [thread overview]
Message-ID: <20020318160228.GA3214@convergence.de> (raw)
In-Reply-To: <Pine.GSO.4.21.0203181644380.5561-100000@vervain.sonytel.be>
On Mon, Mar 18, 2002 at 04:47:13PM +0100, Geert Uytterhoeven wrote:
> On Mon, 18 Mar 2002, Johannes Stezenbach wrote:
> > I'm using binutils-2.12.90.0.1 and gcc-2.95.4-debian, which
> > was recommended here. Read the the thread on "gcc include strangeness"
> > around Feb. 11 for details.
>
> Are you compiling natively, or did you create a cross-compiler using the
> gcc-2.95.4-debian sources?
>
> In the latter case, I'm interested in the magic you used to build the
> cross-compiler, since I can't seem to build a cross-compiler for any arch using
> those sources (2.95.2 was fine).
I built a cross compiler. After 'apt-get source gcc-2.95' I did:
(The instructions in debian/README.cross did not work for me.)
- edit debian/rules.def so that
TARGETS=mips
(README.cross mentions you have to do this)
- run
$ debian/rules patch
- now you have a patched source tree for mips in src-mips, which
configures and builds fine.
HTH,
Johannes
next prev parent reply other threads:[~2002-03-18 16:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-17 20:34 Toolchain question Jan-Benedict Glaw
2002-03-18 15:42 ` Johannes Stezenbach
2002-03-18 15:47 ` Geert Uytterhoeven
2002-03-18 16:02 ` Johannes Stezenbach [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-12 4:59 Nori, Soma Sekhar
2005-04-12 12:07 ` Ralf Baechle
2005-04-11 10:13 Mile Davidovic
2005-04-11 10:13 ` Mile Davidovic
2005-04-11 13:38 ` Ralf Baechle
2002-02-21 12:32 Jan-Benedict Glaw
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=20020318160228.GA3214@convergence.de \
--to=js@convergence.de \
--cc=geert@linux-m68k.org \
--cc=jbglaw@lug-owl.de \
--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