public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Maxim Kuvyrkov <maxim@codesourcery.com>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: linux-m68k@vger.kernel.org, debian-68k@lists.debian.org
Subject: Re: toolchain, was Re: bogl: don't know screen type 1
Date: Sat, 05 Sep 2009 17:31:58 +0400	[thread overview]
Message-ID: <4AA2684E.1080009@codesourcery.com> (raw)
In-Reply-To: <alpine.OSX.2.00.0909050045330.383@silk.local>

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

  parent reply	other threads:[~2009-09-05 13:32 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-31  3:28 bogl: don't know screen type 1 mike
2009-08-31 12:06 ` Stephen R Marenka
2009-08-31 12:58   ` mike
2009-08-31 22:11     ` mike
2009-08-31 22:16       ` mike
2009-09-01 15:17         ` Stephen R Marenka
2009-09-03  1:16           ` mike
2009-09-03  1:22             ` mike
2009-09-03  9:50               ` Maxim Kuvyrkov
2009-09-03 16:41                 ` mike
2009-09-11 20:01               ` Kolbjørn Barmen
2009-09-11 20:25                 ` Geert Uytterhoeven
2009-09-12 10:24                 ` fthain
2009-09-04 15:43           ` toolchain, was " Finn Thain
2009-09-05  1:08             ` Stephen R Marenka
2009-09-05  1:57               ` mike
2009-09-05  2:17                 ` mike
2009-09-05  7:08               ` Petr Stehlik
2009-09-05  8:49               ` Ingo Jürgensmann
2009-09-06  5:07               ` Finn Thain
2009-09-05 13:31             ` Maxim Kuvyrkov [this message]
2009-09-05 16:00               ` mike
2009-09-06 10:00                 ` Finn Thain
2009-09-06  2:37               ` toolchain Finn Thain
2009-09-06 23:09                 ` toolchain Stephen R Marenka
2009-09-06  5:20               ` toolchain Finn Thain
2009-09-08 13:07                 ` toolchain Finn Thain
2009-09-13  3:38               ` toolchain, was Re: bogl: don't know screen type 1 fthain
2009-09-13  5:01                 ` Maxim Kuvyrkov
2009-09-14 10:37                   ` fthain
2009-09-22  5:11                     ` mike
2009-09-22 13:09                       ` benchmarks, was Re: toolchain Finn Thain
2009-09-22 14:51                         ` mike
2009-09-22 15:08                           ` Geert Uytterhoeven
2009-09-28 14:00                       ` toolchain, was Re: bogl: don't know screen type 1 mike
2009-09-28 14:26                         ` debian installation Finn Thain
2009-09-28 14:44                           ` mike
2009-09-29  9:45                             ` mike
2009-09-29 22:23                               ` Rolf Anders

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AA2684E.1080009@codesourcery.com \
    --to=maxim@codesourcery.com \
    --cc=debian-68k@lists.debian.org \
    --cc=fthain@telegraphics.com.au \
    --cc=linux-m68k@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox