linux-mips
[Top] [All Lists]

Re: gcc 3.0 / glibc 2.2.3 cross-toolchain

To: "Bradley D. LaRonde" <brad@ltc.com>
Subject: Re: gcc 3.0 / glibc 2.2.3 cross-toolchain
From: Daniel Jacobowitz <dan@debian.org>
Date: Wed, 8 Aug 2001 16:45:02 -0700
Cc: linux-mips@oss.sgi.com
In-reply-to: <02a401c12063$cde1e830$3501010a@ltc.com>; from brad@ltc.com on Wed, Aug 08, 2001 at 07:42:17PM -0400
References: <02a401c12063$cde1e830$3501010a@ltc.com>
Sender: owner-linux-mips@oss.sgi.com
User-agent: Mutt/1.3.16i
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.

If you want debugging info, of course, it's much more complicated :)

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer

<Prev in Thread] Current Thread [Next in Thread>