From: "smills_ho" <smills_ho@coventive.com>
To: <kumba@gentoo.org>, <linux-mips@linux-mips.org>
Subject: Re: Problem of cross-mipsel-compiler GLIBC-2.3.X
Date: Fri, 9 May 2003 17:40:58 +0800 [thread overview]
Message-ID: <000401c3160f$1a087bf0$d017a8c0@pc208> (raw)
In-Reply-To: 3EBB670E.4020200@gentoo.org
Dear Kumba,
After try several versions of binutils and glibc , it works in crossing
XFree86 4.2.1.
binutils 2.13.2.1 + gcc 3.2.3 + glibc 2.3.2
and some patchs come from debian's packages ( binutils 2.13.90.0.18 ,
gcc-3.2.1,glibc-2.3.1)
Thanks and best regards,
Smills_ho
----- Original Message -----
From: "Kumba" <kumba@gentoo.org>
To: <linux-mips@linux-mips.org>
Sent: Friday, May 09, 2003 4:30 PM
Subject: Re: Problem of cross-mipsel-compiler GLIBC-2.3.X
>
> I'm not quite sure. I don't see how trying it could hurt, maybe it
> will work, maybe it won't. Although, 2.14.90.0.1 was just released as
> well, you might try that, or even CVS Head, as I heard that includes
> last-minute mips fixes. I'm fairly new to the whole cross-compiler
> thing myself, and recently discovered the HOWTO mentioned in your
> previous mail, which I'm looking at to try and get an i686->mips
> cross-compiler going. For now though, my sparc->mips cross-compiler
> works, so it's what I'll rely on the most.
>
> --Kumba
>
>
> smills_ho wrote:
> > Dear Kumba,
> > Should we try this binutils-2.13.90.0.20?
> > We try the version binutils-2.13.90.0.18 (Debian used) and it is failed
on
> > cross-gcc step :-(
> >
> > Thanks and best regards,
> >
> > ----- Original Message -----
> > From: "Kumba" <kumba@gentoo.org>
> > To: <linux-mips@linux-mips.org>
> > Sent: Friday, May 09, 2003 3:29 PM
> > Subject: Re: Problem of cross-mipsel-compiler GLIBC-2.3.X
> >
> >
> >
> >>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
> >>>
> >>
> >>
> >
> >
> >
>
>
WARNING: multiple messages have this Message-ID (diff)
From: "smills_ho" <smills_ho@coventive.com>
To: kumba@gentoo.org, linux-mips@linux-mips.org
Subject: Re: Problem of cross-mipsel-compiler GLIBC-2.3.X
Date: Fri, 9 May 2003 17:40:58 +0800 [thread overview]
Message-ID: <000401c3160f$1a087bf0$d017a8c0@pc208> (raw)
Message-ID: <20030509094058.KChZqOw0Qbct2Cq98v4GPQ02PoygtUK3IZztS3C3TvM@z> (raw)
In-Reply-To: 3EBB670E.4020200@gentoo.org
Dear Kumba,
After try several versions of binutils and glibc , it works in crossing
XFree86 4.2.1.
binutils 2.13.2.1 + gcc 3.2.3 + glibc 2.3.2
and some patchs come from debian's packages ( binutils 2.13.90.0.18 ,
gcc-3.2.1,glibc-2.3.1)
Thanks and best regards,
Smills_ho
----- Original Message -----
From: "Kumba" <kumba@gentoo.org>
To: <linux-mips@linux-mips.org>
Sent: Friday, May 09, 2003 4:30 PM
Subject: Re: Problem of cross-mipsel-compiler GLIBC-2.3.X
>
> I'm not quite sure. I don't see how trying it could hurt, maybe it
> will work, maybe it won't. Although, 2.14.90.0.1 was just released as
> well, you might try that, or even CVS Head, as I heard that includes
> last-minute mips fixes. I'm fairly new to the whole cross-compiler
> thing myself, and recently discovered the HOWTO mentioned in your
> previous mail, which I'm looking at to try and get an i686->mips
> cross-compiler going. For now though, my sparc->mips cross-compiler
> works, so it's what I'll rely on the most.
>
> --Kumba
>
>
> smills_ho wrote:
> > Dear Kumba,
> > Should we try this binutils-2.13.90.0.20?
> > We try the version binutils-2.13.90.0.18 (Debian used) and it is failed
on
> > cross-gcc step :-(
> >
> > Thanks and best regards,
> >
> > ----- Original Message -----
> > From: "Kumba" <kumba@gentoo.org>
> > To: <linux-mips@linux-mips.org>
> > Sent: Friday, May 09, 2003 3:29 PM
> > Subject: Re: Problem of cross-mipsel-compiler GLIBC-2.3.X
> >
> >
> >
> >>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
> >>>
> >>
> >>
> >
> >
> >
>
>
next prev parent reply other threads:[~2003-05-09 9:40 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
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 [this message]
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='000401c3160f$1a087bf0$d017a8c0@pc208' \
--to=smills_ho@coventive.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox