From mboxrd@z Thu Jan 1 00:00:00 1970 From: Maxim Kuvyrkov Subject: Re: toolchain, was Re: bogl: don't know screen type 1 Date: Sat, 05 Sep 2009 17:31:58 +0400 Message-ID: <4AA2684E.1080009@codesourcery.com> References: <8259f0250908302028n9b0cb56td402539007736fce@mail.gmail.com> <20090831120617.GA1114@marenka.net> <8259f0250908310558l3ddd5fam7d15946a7c1e8572@mail.gmail.com> <8259f0250908311511h77270544vb2dc3dd383f1add8@mail.gmail.com> <8259f0250908311516r49e54c7fi44ead0f040cade30@mail.gmail.com> <20090901151747.GB27514@marenka.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mail.codesourcery.com ([65.74.133.4]:39511 "EHLO mail.codesourcery.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751426AbZIENcF (ORCPT ); Sat, 5 Sep 2009 09:32:05 -0400 In-Reply-To: Sender: linux-m68k-owner@vger.kernel.org List-Id: linux-m68k@vger.kernel.org To: Finn Thain Cc: linux-m68k@vger.kernel.org, debian-68k@lists.debian.org Finn Thain wrote: ... > But in that post (June 28) Maxim recommends using mainline binutils, and > since then we have HJL binutils-2.19.51.0.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. > 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. > 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@. -- Maxim