From: Andreas Jaeger <aj@suse.de>
To: "Salisbury, Roger" <Roger.Salisbury@team.telstra.com>
Cc: "'Maciej W. Rozycki'" <macro@ds2.pg.gda.pl>,
Ralf Baechle <ralf@oss.sgi.com>,
linux-mips@oss.sgi.com, linux-mips@fnet.fr
Subject: Re: /usr/bin/file
Date: Tue, 14 Aug 2001 09:16:36 +0200 [thread overview]
Message-ID: <ho8zgn9kmj.fsf@gee.suse.de> (raw)
In-Reply-To: <C1CCF0351229D311BBEB0008C75B9A8A02CAFAD3@ntmsg0080.corpmail.telstra.com.au> ("Salisbury, Roger"'s message of "Tue, 14 Aug 2001 11:40:48 +1000")
"Salisbury, Roger" <Roger.Salisbury@team.telstra.com> writes:
> where do I get "libtoolize"
>
> Still trying to update everything.
>
> binutils-2.9.5.0.37 seems ok. although runtest not found.( needs testsuite,
> which needs DejaGnu from ftp ://gcc.gnu.org/pub/gcc/infrastructure BUT the
> site is currently down.
> glibc-2.2.3 needs gcc-3.0 it seems. (checking version of gcc...
> egcs-2.91.66, bad ...*** Some critical program is missing or too old
> )
>
> gcc-3.0 needs rectification in [libgcc_s.so] & [libgcc.a] it seems (see
> make error below!)
GCC 3.0 will not compile a correct glibc at all, wait for GCC 3.0.1
and glibc 2.2.5 and read the glibc announcements,
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next prev parent reply other threads:[~2001-08-14 7:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-14 1:40 /usr/bin/file Salisbury, Roger
2001-08-14 5:26 ` /usr/bin/file Ralf Baechle
2001-08-14 7:16 ` Andreas Jaeger [this message]
2001-08-16 7:56 ` /usr/bin/file Maciej W. Rozycki
[not found] <C1CCF0351229D311BBEB0008C75B9A8A02CAFACE@ntmsg0080.corpmail.telstra.com.au>
2001-08-10 11:20 ` /usr/bin/file Ralf Baechle
2001-08-10 13:37 ` /usr/bin/file Maciej W. Rozycki
2001-08-10 14:49 ` /usr/bin/file Ralf Baechle
2001-08-13 11:32 ` /usr/bin/file Maciej W. Rozycki
2001-08-13 15:52 ` /usr/bin/file Ralf Baechle
2001-08-13 16:27 ` /usr/bin/file Maciej W. Rozycki
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=ho8zgn9kmj.fsf@gee.suse.de \
--to=aj@suse.de \
--cc=Roger.Salisbury@team.telstra.com \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
--cc=ralf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.