From: Ralf Baechle <ralf@oss.sgi.com>
To: Florian Lohoff <flo@rfc822.org>
Cc: "Gleb O. Raiko" <raiko@niisi.msk.ru>,
linux-mips@oss.sgi.com, linux-mips@fnet.fr,
linux-origin@oss.sgi.com
Subject: Re: libc upgrade
Date: Tue, 26 Sep 2000 23:06:50 +0200 [thread overview]
Message-ID: <20000926230650.B10991@bacchus.dhis.org> (raw)
In-Reply-To: <20000926123600.A413@paradigm.rfc822.org>; from flo@rfc822.org on Tue, Sep 26, 2000 at 12:36:00PM +0200
On Tue, Sep 26, 2000 at 12:36:00PM +0200, Florian Lohoff wrote:
> > Well, another question. Ralf uploaded cross tools rpms year ago. Does
> > anybody have native rmps for big endian ? Also, does anybody have cross
> > tools for sparc glibc 2.1 (RH6.x sparc distribution) ? I can't compile
> > cross gcc on my Ultra, it seems like a bug in the sparc compiler, the
> > process fails in parsing an enum decl in a header.
>
> I tried to compile cross gcc/binutils from CVS a couple of times
> for Linux/Sparc (Ultra) which didnt work as somewhere in the
> middle the beast meant to use the native "as" instead of
> mipsel-linux-as
gcc tries to run as on <prefix>/lib/gcc-lib/<target>/<version>/as, then
<prefix>/<target>/bin/as, then the native as from $PATH. So check if you
were using the same target configuration name (mips-linux and
mips-unknown-linux-gnu are different!) for both gcc and binutils.
Ralf
next prev parent reply other threads:[~2000-09-26 21:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-22 13:26 libc upgrade Ralf Baechle
2000-09-25 9:24 ` Florian Lohoff
2000-09-25 11:20 ` Ralf Baechle
2000-09-25 14:15 ` Florian Lohoff
2000-09-25 20:14 ` Ralf Baechle
2000-09-25 23:04 ` Florian Lohoff
2000-09-26 0:46 ` Ralf Baechle
2000-09-26 8:37 ` Gleb O. Raiko
2000-09-26 10:36 ` Florian Lohoff
2000-09-26 21:06 ` Ralf Baechle [this message]
2000-09-26 17:48 ` Keith M Wesolowski
2000-09-26 8:30 ` Gleb O. Raiko
2000-09-26 22:47 ` 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=20000926230650.B10991@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=flo@rfc822.org \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@oss.sgi.com \
--cc=linux-origin@oss.sgi.com \
--cc=raiko@niisi.msk.ru \
/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