On Sat, 5 Sep 2009, Maxim Kuvyrkov wrote:
> Finn Thain wrote:
> > But in that post (June 28) Maxim recommends using mainline binutils,
> > and since then we have HJL binutils-18.104.22.168.14 released, "...based
> > on binutils 2009 0722 in CVS on sourceware.org..." So I guess I should
> > start there.
> The last binutils TLS patches went in on 2009-08-26; the patches fixed
> generation of invalid TLS relocations.
OK. Debian has 22.214.171.12490827-1 in the sid archive. I wonder if it has
been built yet?
> > I understand that the current GCC (4.4) lacks the necessary patches,
> > and 4.5 is still uncooked (and that's a scary prospect). Can someone
> > confirm that this is the necessary patch for 4.4:
> > http://gcc.gnu.org/ml/gcc-patches/2009-05/msg01024.html
> I think GCC 4.4 should be good enough.
> > As for eglibc, there are a number of branches listed here,
> > http://www.eglibc.org/repository
> > The question is, which branch, snapshot or release might meet be suitable?
> EGLIBC does not yet have NPTL patches checked in, they are in review on
> libc-ports@. Once the review is finished, I will likely backport the
> patches from EGLIBC trunk to 2.10 branch.
I guess I'll wait for that, and then perhaps look into patching 2.9 if
that turns out to be straight forward. (Debian has 2.10 in the
experimental archive, 2.9 (more or less) in stable and testing.)
> > With this information, I could attempt to build a toolchain from
> > upstream sources, or figure out whether or not the debian archive has
> > the necessary source packages...
> You will also need a patch for kernel, posted on linux-m68k@.
Thanks for the update.
> To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
> the body of a message to email@example.com
> More majordomo info at http://vger.kernel.org/majordomo-info.html