Hi Josh, Excerpts from Josh Boyer's message of Fri Oct 01 21:36:35 +1000 2010: > Aside from my general "uh, why?" stance, I'm very very hesitant to > integrate anything in the kernel that doesn'.t have released patches > on the toolchain side.
As I said the kernel can be built today with an unpatched toolchain targetted at powerpcle-elf, the new powerpcle-linux target is mainly required for userspace, but yes I want to get those patches out as soon as possible. > Also, which uClibc? The old and crusty uClibc that uses the horrible > linuxthreads, or the somewhat less crusty that just switched to NPTL > (which hasn't been verified on normal PowerPC that I recall). Why not > use glibc... As Ben said this was for a proof of concept and changing uClibc to support it was quite literally a one line change. I've been using stable packages as my base on the toolchain side of things (gcc 4.4.4, binutils 2.20.1 and uClibc 0.9.31) so uClibc is still using linuxthreads since they haven't released a version with NPTL yet. > I'm not meeting to detract here, but the Kconfig should be dependent > on && BROKEN until the above is fixed. Good point. Cheers, -Ian _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev