From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-mips@oss.sgi.com
Subject: Toolchain question
Date: Thu, 21 Feb 2002 13:32:22 +0100 [thread overview]
Message-ID: <20020221133222.J21530@lug-owl.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 399 bytes --]
Hi!
I'm to build a new toolchain and looked around. There's still the
cross-all-20010423.tar package on oss.sgi.com. Is it still
recommened to use this, or am I better off using a current
CVS co of binutils and gcc?
MfG, JBG
--
Jan-Benedict Glaw . jbglaw@lug-owl.de . +49-172-7608481
-- New APT-Proxy written in shell script --
http://lug-owl.de/~jbglaw/software/ap2/
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next reply other threads:[~2002-02-21 13:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 12:32 Jan-Benedict Glaw [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2005-04-11 10:13 Mile Davidovic
2005-04-11 10:13 ` Mile Davidovic
2005-04-11 13:38 ` Ralf Baechle
2005-04-12 4:59 Nori, Soma Sekhar
2005-04-12 12:07 ` Ralf Baechle
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=20020221133222.J21530@lug-owl.de \
--to=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