-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Christian Eggers wrote: >>> I've tried to build an ARM NPTL toolchain with buildroot. Therefore I've >>> added a new option for using the head of the nptl-branch of uclibc to >>> buildroot-2009.02. >>> >>> Buildroot-Settings: >>> Target Architecture: arm >>> Target Architecture-Variant: arm920t >>> Target ABI: oabi >>> Toolchain->Thread library implementation: NPTL >>> >>> With this the build of uclibc fails: >>> >>> ----------------------- >>> >>>> LD libuClibc-0.9.30-svn.so >>>> libc/libc_so.a(close.oS):(.ARM.exidx+0x0): undefined reference to >>>> `__aeabi_unwind_cpp_pr0' collect2: ld returned 1 exit status >> This is due to the way you build the toolchain. These symbols are in libgcc > > Which way do you recommend? I thought that buildroot is the prefered way to > build a cross-toolchain with uClibc, isn't it? Do you use a shell script? > > regards > Christian > Hi, recently I've debugged some problem in uclibc-nptl built from buildroot caused by a misconfiguration of the cross compiler in particular for the stack uniwind functions. In NPTL the stack unwinding must use dwarf. The buildroot toolchain is not able to correctly build a libgcc with the proper stack iunwind implementations. I have a tested patch for the buildroot that hopefully I'll push back to them soon. So be careful with NPTL when using buildroot.
Cheers, Carmelo > _______________________________________________ > uClibc mailing list > [email protected] > http://lists.busybox.net/mailman/listinfo/uclibc > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAknRx3IACgkQoRq/3BrK1s9+nQCeKT8nJQucQXmhVg8F7UrqF/+R eiEAnRVaeiD7c+HunesSFOL22RlrMZJW =/ob7 -----END PGP SIGNATURE----- _______________________________________________ uClibc mailing list [email protected] http://lists.busybox.net/mailman/listinfo/uclibc
