All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kumba <kumba@gentoo.org>
To: linux-mips@linux-mips.org
Subject: Re: Problem of cross-mipsel-compiler GLIBC-2.3.X
Date: Fri, 09 May 2003 03:29:10 -0400	[thread overview]
Message-ID: <3EBB58C6.3070604@gentoo.org> (raw)
In-Reply-To: <1052464867.2485.3.camel@ghostwheel.sfbay.redhat.com>

Oddly enough, I followed these basic steps and wound up with a working 
cross-compiler from sparc64 -> mipseb (Sun Blade 100 to mips 
big-endian).  Gcc nor glibc gave me any issues.....However, when I tried 
the same exact steps on i686, glibc complained about libgcc not being 
available, among other things.  It's got me baffled, but I'm not exactly 
complaining.  Currently, it's gcc-3.2.3 (propolice patched) + 
glibc-2.3.2 + binutils-2.13.90.0.20, which it'll get rebuilt for the new 
binutils 2.14.

--Kumba



Eric Christopher wrote:
> On Thu, 2003-05-08 at 19:05, smills_ho wrote:
> 
>>Dear All,
>>    I want to make a cross-compilered glibc-2.3.x and I get the source from
>>ftp.gun.org. GCC version is 3.2.3, binutils is 2.13.2.1. The step is as
>>following:
>>
>>1. Try to build binutils
>>2. Try to make static GCC
>>3. Try to make glibc -----> Then it is failed
>>
>>Is there anybody know what's going on or somebody had successfully to build
>>the crossed glibc-2.3.x?
> 
> 
> A host cross host compiler for linux systems is a little more involved
> than this :)
> 
> However, I don't know where you went wrong since you really didn't
> provide much in the way of information as to what you did or where it
> failed.
> 
> -eric
> 

  reply	other threads:[~2003-05-09  7:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-01  5:39 GCC -O2 failure for mipsel Fuxin Zhang
2003-05-01  8:27 ` Andrew Haley
2003-05-01  8:41   ` Fuxin Zhang
2003-05-01  8:46     ` Andrew Haley
2003-05-01  8:50       ` Greg Lindahl
2003-05-09  2:05         ` Problem of cross-mipsel-compiler GLIBC-2.3.X smills_ho
2003-05-09  2:05           ` smills_ho
2003-05-09  7:21           ` Eric Christopher
2003-05-09  7:29             ` Kumba [this message]
2003-05-09  8:15               ` smills_ho
2003-05-09  8:15                 ` smills_ho
2003-05-09  8:30                 ` Kumba
2003-05-09  9:40                   ` smills_ho
2003-05-09  9:40                     ` smills_ho
2003-05-09 11:20                   ` Guido Guenther
2003-05-09  8:10             ` smills_ho
2003-05-09  8:10               ` smills_ho
2003-05-09 17:13               ` Eric Christopher
2003-05-01 11:00       ` GCC -O2 failure for mipsel Andrew Pinski

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=3EBB58C6.3070604@gentoo.org \
    --to=kumba@gentoo.org \
    --cc=linux-mips@linux-mips.org \
    /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.