building GLIBC-2.4 header problem with ARM/NPTL/EABI

Martin Guy martinwguy@gmail.com
Fri Apr 21 14:38:00 GMT 2006


Forwarding to the list for their info...

On 4/20/06, Wu Bridge <mingqiao.wu@gmail.com> wrote:
> There is an option "--enable-add-ons=ports,nptl" when building glibc
> header. This option caused the error. I know the ports are used to
> point the directory glibc-ports-2.4 unpacked. Well, can't NPTL be
> supported by this way?

> I have confirmed "--enable-add-ons=ports,nptl" should not be used to
> build glibc header. I used "--enable-add-ons=ports," and got the
> toolchain finally. (unfortunately, it has a lot of problems when
> building modules and applications)

Hi
   linuxthreads and nptl are two different implementations of the
threading mechanism. Up to glibc-2.3.6 you could use on or the other.
From glibc-2.4 linuxthreads does not exist, so NPTL is obligatory.
   I currently build on two Debian x86 machines. On mine the build
works completely. It throws out "TLS is required" messages making the
gilbc headers, but carries on anyway.
   On the other, the "TLS is required" stops the build. I don't know why.
   My only current lead is that the versions of "make" are slightly
different; mine is debian testing+stable updated to a few days ago
(make 3.81rc2); the other is the same + unstable, last upgraded in
January. (make 3.81beta4).
   I will be looking at this today; it may be that some of the options
are not being passed to the glibc-header-making step.
   I also have "Kernel version is too old" coming out as a #error in
the logs. Again, I need to look into this.

     M

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



More information about the crossgcc mailing list