From: "Bradley D. LaRonde" <brad@ltc.com>
To: "Daniel Jacobowitz" <dan@debian.org>
Cc: <linux-mips@oss.sgi.com>
Subject: Re: gcc 3.0 / glibc 2.2.3 cross-toolchain
Date: Wed, 8 Aug 2001 19:58:57 -0400 [thread overview]
Message-ID: <02ca01c12066$164e5570$3501010a@ltc.com> (raw)
In-Reply-To: 20010808164502.A6966@nevyn.them.org
----- Original Message -----
From: "Daniel Jacobowitz" <dan@debian.org>
To: "Bradley D. LaRonde" <brad@ltc.com>
Cc: <linux-mips@oss.sgi.com>
Sent: Wednesday, August 08, 2001 7:45 PM
Subject: Re: gcc 3.0 / glibc 2.2.3 cross-toolchain
> On Wed, Aug 08, 2001 at 07:42:17PM -0400, Bradley D. LaRonde wrote:
> > I have spent quite a bit of time trying to get a gcc 3.0 / glibc 2.2.3
> > cross-toolchain working. I am not a Toolchain Builder, but I really
wanted
> > to try this combo and I don't see any way around building it myself.
> >
> > I've had some success. Everything seems to build fine. However, when I
try
> > to run a simple "hello world" dynamically linked with glibc, I get this:
> >
> > <myprogram>: error while loading shared libraries: failed to map
> > segment from shared object: cannot load shared object file: Invalid
> > argument
> >
> > I think it is trying to load libc.so.6, which is in my root in /lib/,
> > symlinked to libc-2.2.3.so, and so is ld.so.1, symlinked to ld-2.2.3.so.
> >
> > I feel like I am pretty close, but I am starting to get discouraged and
> > could really use some help. I really am clueless about what
> > should/shouldn't work. I'm trying to do this based on bits and pieces
of
> > information that I've collected from countless sources. I have heard
that
> > gcc 3.0 isn't really "working", but I still want to try.
> >
> > Here is what I've used:
> >
> > * binutils-2.11.90.0.25.tar.gz (extracted from H. J. Lu's
> > srpm on oss.sgi.com; I've tried others also)
> > * gcc-3.0.tar.gz (released version - no patches)
> > * glibc-linuxthreads-2.2.3.tar.gz (released version - no
> > patches; glibc didn't want to configure without this)
> > * glibc-2.2.3.tar.gz (released version)
>
> You're missing the patch to change MAP_BASE_ADDR. You need that.
> Something as simple as changing it to 0 will work for you, since you're
> building everything yourself.
I tried applying the patch that H. J. Lu posted on linux-mips that contains
that fix, but then glibc would compile. I'll try it again - maybe I messed
something up. If that doesn't work, I'll try the simple fix. Thanks.
Regards,
Brad
WARNING: multiple messages have this Message-ID (diff)
From: "Bradley D. LaRonde" <brad@ltc.com>
To: Daniel Jacobowitz <dan@debian.org>
Cc: linux-mips@oss.sgi.com
Subject: Re: gcc 3.0 / glibc 2.2.3 cross-toolchain
Date: Wed, 8 Aug 2001 19:58:57 -0400 [thread overview]
Message-ID: <02ca01c12066$164e5570$3501010a@ltc.com> (raw)
Message-ID: <20010808235857.mdyMCkFq513iFeLOL9Cav_2E9yBYzSHea56aTzauhIk@z> (raw)
In-Reply-To: 20010808164502.A6966@nevyn.them.org
----- Original Message -----
From: "Daniel Jacobowitz" <dan@debian.org>
To: "Bradley D. LaRonde" <brad@ltc.com>
Cc: <linux-mips@oss.sgi.com>
Sent: Wednesday, August 08, 2001 7:45 PM
Subject: Re: gcc 3.0 / glibc 2.2.3 cross-toolchain
> On Wed, Aug 08, 2001 at 07:42:17PM -0400, Bradley D. LaRonde wrote:
> > I have spent quite a bit of time trying to get a gcc 3.0 / glibc 2.2.3
> > cross-toolchain working. I am not a Toolchain Builder, but I really
wanted
> > to try this combo and I don't see any way around building it myself.
> >
> > I've had some success. Everything seems to build fine. However, when I
try
> > to run a simple "hello world" dynamically linked with glibc, I get this:
> >
> > <myprogram>: error while loading shared libraries: failed to map
> > segment from shared object: cannot load shared object file: Invalid
> > argument
> >
> > I think it is trying to load libc.so.6, which is in my root in /lib/,
> > symlinked to libc-2.2.3.so, and so is ld.so.1, symlinked to ld-2.2.3.so.
> >
> > I feel like I am pretty close, but I am starting to get discouraged and
> > could really use some help. I really am clueless about what
> > should/shouldn't work. I'm trying to do this based on bits and pieces
of
> > information that I've collected from countless sources. I have heard
that
> > gcc 3.0 isn't really "working", but I still want to try.
> >
> > Here is what I've used:
> >
> > * binutils-2.11.90.0.25.tar.gz (extracted from H. J. Lu's
> > srpm on oss.sgi.com; I've tried others also)
> > * gcc-3.0.tar.gz (released version - no patches)
> > * glibc-linuxthreads-2.2.3.tar.gz (released version - no
> > patches; glibc didn't want to configure without this)
> > * glibc-2.2.3.tar.gz (released version)
>
> You're missing the patch to change MAP_BASE_ADDR. You need that.
> Something as simple as changing it to 0 will work for you, since you're
> building everything yourself.
I tried applying the patch that H. J. Lu posted on linux-mips that contains
that fix, but then glibc would compile. I'll try it again - maybe I messed
something up. If that doesn't work, I'll try the simple fix. Thanks.
Regards,
Brad
next prev parent reply other threads:[~2001-08-08 23:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-08 23:42 gcc 3.0 / glibc 2.2.3 cross-toolchain Bradley D. LaRonde
2001-08-08 23:42 ` Bradley D. LaRonde
2001-08-08 23:45 ` Daniel Jacobowitz
2001-08-08 23:58 ` Bradley D. LaRonde [this message]
2001-08-08 23:58 ` Bradley D. LaRonde
2001-08-09 2:44 ` Bradley D. LaRonde
2001-08-09 2:44 ` Bradley D. LaRonde
2001-08-09 3:49 ` Bradley D. LaRonde
2001-08-09 3:49 ` Bradley D. LaRonde
2001-08-09 13:03 ` Arnaud Rolly
2001-08-09 7:11 ` Ilya Volynets
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='02ca01c12066$164e5570$3501010a@ltc.com' \
--to=brad@ltc.com \
--cc=dan@debian.org \
--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 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.