More crosstool-0.42-glibc-2.4-gcc-4.1.0-nptl

[Robert Schwebel]

Michael, 

On Wed, Apr 26, 2006 at 10:45:19PM -0700, Michael K. Edwards wrote:
> The attached patch (for crosstool 0.42) is a variation on Martin Guy's
> ARM EABI / NPTL/TLS patch (posted April 18).  It has some additional
> fixes for things I ran into when building the C++ cross-compiler and
> Linux 2.6.16.11, optimized for a particular core (arm926ej-s).

I've tried your patch on a debian unstable machine with gcc-4.0.3,
2.16.1cvs20060117-1 and glibc-2.3.6-7 and get this error from the glibc
startfiles stage: 

running configure fragment for ports/sysdeps/unix/sysv/linux/arm/eabi/nptl
running configure fragment for ports/sysdeps/unix/sysv/linux/arm/eabi
running configure fragment for nptl/sysdeps/pthread
configure: error: working compiler support for visibility attribute is required

> A few words about using crosstool on an ancient host OS:

I think the tools on the development host should be reasonably new. 

> Make sure that you have quite recent versions of gcc and binutils
> installed on your development host; they are needed not only to
> compile the tools but also to fake some of the steps involved in
> massaging the kernel headers, so they need to match the cross
> configuration in a couple of respects (notably
> --enable-threads=posix).  This may require a couple of rounds of
> upgrading if your dev host OS is old; I climbed from gcc 3.2 to 3.3.6
> to 4.1.0 with a couple of iterations on binutils-2.16.92 and gcc-4.1.0
> to get the threading right.  These native tools should be in your PATH
> ahead of whatever came with your operating system.

Did you see the problem above with the "old" toolchains? 

Robert
-- 
 Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry
   Handelsregister:  Amtsgericht Hildesheim, HRA 2686
     Hannoversche Str. 2, 31134 Hildesheim, Germany
   Phone: +49-5121-206917-0 |  Fax: +49-5121-206917-9


--
For unsubscribe information see http://sourceware.org/lists.html#faq