gcc 3.0 / glibc 2.2.3 cross-toolchain

gcc 3.0 / glibc 2.2.3 cross-toolchain

[Bradley D. LaRonde]

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)

plus a tiny patch to glibc that looks like:

--- libc-04052001/sysdeps/mips/mipsel/rtld-parms Sat Jul 12 18:26:15 1997
+++ libc-04052001-patched/sysdeps/mips/mipsel/rtld-parms Fri Apr  6 09:23:27
2001
@@ -1,3 +1,3 @@
 ifndef rtld-oformat
-rtld-oformat = elf32-littlemips
+rtld-oformat = elf32-tradlittlemips
 endif

I built everything on my i386 Debian 2.2 box as follows:

Build the mipsel cross-binutils

  tar -xzf binutils-2.11.90.0.25.tar.gz
  mkdir mipsel-binutils
  cd mipsel-binutils

  ../binutils-2.11.2/configure --target=mipsel-linux \
    --libdir='${exec_prefix}'/mipsel-linux/i386-linux/lib

  make
  make install
  cd ..

Build the mipsel cross-gcc:

  tar -xzf gcc-3.0.tar.gz
  mkdir mipsel-gcc
  cd mipsel-gcc

  ../gcc-3.0/configure --target=mipsel-linux \
     --enable-languages=c --disable-shared

  make
  make install
  cd ..

Install the kernel headers

  mkdir /usr/local/mipsel-linux/include
  cp -r $LINUX_SRC/include/linux /usr/local/mipsel-linux/include
  cp -r $LINUX_SRC/include/asm-mips /usr/local/mipsel-linux/include/asm

Build glibc:

  tar -xzf glibc-2.2.3
  cd glibc-2.2.3
  patch -p1 -i../elf32-tradlittlemips.diff
  tar -xzf ../glibc-linuxthreads-2.2.3.tar.gz
  cd ..
  mkdir mipsel-glibc
  cd mipsel-glibc

  ../glibc-2.2.3/configure --build=i686-linux --host=mipsel-linux \
    --enable-add-ons --prefix=/usr/local/mipsel-linux

  make
  make install
  cd ..

Thanks.

Regards,
Brad

gcc 3.0 / glibc 2.2.3 cross-toolchain

[Bradley D. LaRonde]

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)

plus a tiny patch to glibc that looks like:

--- libc-04052001/sysdeps/mips/mipsel/rtld-parms Sat Jul 12 18:26:15 1997
+++ libc-04052001-patched/sysdeps/mips/mipsel/rtld-parms Fri Apr  6 09:23:27
2001
@@ -1,3 +1,3 @@
 ifndef rtld-oformat
-rtld-oformat = elf32-littlemips
+rtld-oformat = elf32-tradlittlemips
 endif

I built everything on my i386 Debian 2.2 box as follows:

Build the mipsel cross-binutils

  tar -xzf binutils-2.11.90.0.25.tar.gz
  mkdir mipsel-binutils
  cd mipsel-binutils

  ../binutils-2.11.2/configure --target=mipsel-linux \
    --libdir='${exec_prefix}'/mipsel-linux/i386-linux/lib

  make
  make install
  cd ..

Build the mipsel cross-gcc:

  tar -xzf gcc-3.0.tar.gz
  mkdir mipsel-gcc
  cd mipsel-gcc

  ../gcc-3.0/configure --target=mipsel-linux \
     --enable-languages=c --disable-shared

  make
  make install
  cd ..

Install the kernel headers

  mkdir /usr/local/mipsel-linux/include
  cp -r $LINUX_SRC/include/linux /usr/local/mipsel-linux/include
  cp -r $LINUX_SRC/include/asm-mips /usr/local/mipsel-linux/include/asm

Build glibc:

  tar -xzf glibc-2.2.3
  cd glibc-2.2.3
  patch -p1 -i../elf32-tradlittlemips.diff
  tar -xzf ../glibc-linuxthreads-2.2.3.tar.gz
  cd ..
  mkdir mipsel-glibc
  cd mipsel-glibc

  ../glibc-2.2.3/configure --build=i686-linux --host=mipsel-linux \
    --enable-add-ons --prefix=/usr/local/mipsel-linux

  make
  make install
  cd ..

Thanks.

Regards,
Brad

Re: gcc 3.0 / glibc 2.2.3 cross-toolchain

[Daniel Jacobowitz]

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

Re: gcc 3.0 / glibc 2.2.3 cross-toolchain

[Bradley D. LaRonde]

----- 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

Re: gcc 3.0 / glibc 2.2.3 cross-toolchain

[Bradley D. LaRonde]

----- 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

Re: gcc 3.0 / glibc 2.2.3 cross-toolchain

[Bradley D. LaRonde]

Woohoo!  It works!  Thanks!  I was using H. J. Lu's first patch and that was
broken.  I found the second patch and it worked, except it left the first
line in rtld-ldscript.in, when it really should have removed the file
entirely.  Looks like it's right in the glibc CVS though.

Regards,
Brad

----- Original Message -----
From: "Bradley D. LaRonde" <brad@ltc.com>
To: "Daniel Jacobowitz" <dan@debian.org>
Cc: <linux-mips@oss.sgi.com>
Sent: Wednesday, August 08, 2001 7:58 PM
Subject: Re: gcc 3.0 / glibc 2.2.3 cross-toolchain


> ----- 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

Re: gcc 3.0 / glibc 2.2.3 cross-toolchain

[Bradley D. LaRonde]

Woohoo!  It works!  Thanks!  I was using H. J. Lu's first patch and that was
broken.  I found the second patch and it worked, except it left the first
line in rtld-ldscript.in, when it really should have removed the file
entirely.  Looks like it's right in the glibc CVS though.

Regards,
Brad

----- Original Message -----
From: "Bradley D. LaRonde" <brad@ltc.com>
To: "Daniel Jacobowitz" <dan@debian.org>
Cc: <linux-mips@oss.sgi.com>
Sent: Wednesday, August 08, 2001 7:58 PM
Subject: Re: gcc 3.0 / glibc 2.2.3 cross-toolchain


> ----- 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

Re: gcc 3.0 / glibc 2.2.3 cross-toolchain

[Bradley D. LaRonde]

I've chronicled my cross-toolchain mips-adventures at:

http://www.ltc.com/~brad/mips/mipsel-linux-cross-toolchain-building.txt

I included a copy of the glibc patch that has the MAP_BASE_ADDR fix in it in
the same directory, namely:

http://www.ltc.com/~brad/mips/

Regards,
Brad

----- Original Message -----
From: "Bradley D. LaRonde" <brad@ltc.com>
To: "Bradley D. LaRonde" <brad@ltc.com>; "Daniel Jacobowitz"
<dan@debian.org>
Cc: <linux-mips@oss.sgi.com>
Sent: Wednesday, August 08, 2001 10:44 PM
Subject: Re: gcc 3.0 / glibc 2.2.3 cross-toolchain


> Woohoo!  It works!  Thanks!  I was using H. J. Lu's first patch and that
was
> broken.  I found the second patch and it worked, except it left the first
> line in rtld-ldscript.in, when it really should have removed the file
> entirely.  Looks like it's right in the glibc CVS though.
>
> Regards,
> Brad
>
> ----- Original Message -----
> From: "Bradley D. LaRonde" <brad@ltc.com>
> To: "Daniel Jacobowitz" <dan@debian.org>
> Cc: <linux-mips@oss.sgi.com>
> Sent: Wednesday, August 08, 2001 7:58 PM
> Subject: Re: gcc 3.0 / glibc 2.2.3 cross-toolchain
>
>
> > ----- 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

Re: gcc 3.0 / glibc 2.2.3 cross-toolchain

[Bradley D. LaRonde]

I've chronicled my cross-toolchain mips-adventures at:

http://www.ltc.com/~brad/mips/mipsel-linux-cross-toolchain-building.txt

I included a copy of the glibc patch that has the MAP_BASE_ADDR fix in it in
the same directory, namely:

http://www.ltc.com/~brad/mips/

Regards,
Brad

----- Original Message -----
From: "Bradley D. LaRonde" <brad@ltc.com>
To: "Bradley D. LaRonde" <brad@ltc.com>; "Daniel Jacobowitz"
<dan@debian.org>
Cc: <linux-mips@oss.sgi.com>
Sent: Wednesday, August 08, 2001 10:44 PM
Subject: Re: gcc 3.0 / glibc 2.2.3 cross-toolchain


> Woohoo!  It works!  Thanks!  I was using H. J. Lu's first patch and that
was
> broken.  I found the second patch and it worked, except it left the first
> line in rtld-ldscript.in, when it really should have removed the file
> entirely.  Looks like it's right in the glibc CVS though.
>
> Regards,
> Brad
>
> ----- Original Message -----
> From: "Bradley D. LaRonde" <brad@ltc.com>
> To: "Daniel Jacobowitz" <dan@debian.org>
> Cc: <linux-mips@oss.sgi.com>
> Sent: Wednesday, August 08, 2001 7:58 PM
> Subject: Re: gcc 3.0 / glibc 2.2.3 cross-toolchain
>
>
> > ----- 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

Re: gcc 3.0 / glibc 2.2.3 cross-toolchain

[Arnaud Rolly]

Le Mercredi  8 Août 2001 23:49, vous avez écrit :
> I've chronicled my cross-toolchain mips-adventures at:
>
> http://www.ltc.com/~brad/mips/mipsel-linux-cross-toolchain-building.txt
>
> I included a copy of the glibc patch that has the MAP_BASE_ADDR fix in it
> in the same directory, namely:
>
> http://www.ltc.com/~brad/mips/
>
> Regards,
> Brad
It would be great to have a patch repository, for example just a directory on 
the FTP of oss.sgi.com

Re: gcc 3.0 / glibc 2.2.3 cross-toolchain

[Ilya Volynets]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I offered something along these lines a while ago. I even started a little site.
Unfortunately I don't have enough time to keep up with current toolchain
patches, etc. myself, but if people send me patches, along with comments,
I'll post them at my site.
On Thursday 09 August 2001 06:03, Arnaud Rolly wrote:
> Le Mercredi  8 AoШt 2001 23:49, vous avez Иcrit :
> > I've chronicled my cross-toolchain mips-adventures at:
> >
> > http://www.ltc.com/~brad/mips/mipsel-linux-cross-toolchain-building.txt
> >
> > I included a copy of the glibc patch that has the MAP_BASE_ADDR fix in it
> > in the same directory, namely:
> >
> > http://www.ltc.com/~brad/mips/
> >
> > Regards,
> > Brad
>
> It would be great to have a patch repository, for example just a directory
> on the FTP of oss.sgi.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAjtyN5kACgkQtKh84cA8u2lORwCcDr0csXgikuVFizIgBXJgncPv
zpQAoIGtXsSE7WMiBP0XODyWhEMhj9zb
=VJLD
-----END PGP SIGNATURE-----