public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Finn Thain <fthain@telegraphics.com.au>
To: Stephen R Marenka <stephen@marenka.net>
Cc: debian-68k@lists.debian.org, linux-m68k@vger.kernel.org
Subject: Re: toolchain, was Re: bogl: don't know screen type 1
Date: Sun, 6 Sep 2009 15:07:02 +1000 (EST)	[thread overview]
Message-ID: <alpine.OSX.2.00.0909061457300.415@silk.local> (raw)
In-Reply-To: <20090905010830.GA14809@marenka.net>



On Fri, 4 Sep 2009, Stephen R Marenka wrote:

> On Sat, Sep 05, 2009 at 01:43:14AM +1000, Finn Thain wrote:
> > 
> > The patches posted to the binutils mailing list are incomplete. The 
> > binutils patch at
> > http://people.debian.org/~smarenka/m68k/tls/
> > is broken according to Kolla:
> > http://lists.debian.org/debian-68k/2009/07/msg00001.html
> > 
> > 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.
> > 
> > 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
> > Presumably not this one?
> > http://people.debian.org/~smarenka/m68k/tls/gcc_patch2
> > (and gcc_patch1 is clearly broken... perhaps it was actually the same 
> > thing before being mangled... Stephen, I don't think this "/tls" directory 
> > is helping any.)
> 
> Shall I remove it then?

I'd remove it.

The gcc commit in question is this one,
http://gcc.gnu.org/viewcvs?view=revision&revision=147654
which appears to be the very one in the mailing list archive at the URL 
above (you can download a raw version at that URL).

A quick visual shows that tls/gcc_patch2 doesn't match the commit (the 
revision numbers in the diff confirm that it is older).

Finn

  parent reply	other threads:[~2009-09-06  5:07 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 [this message]
2009-09-05 13:31             ` Maxim Kuvyrkov
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=alpine.OSX.2.00.0909061457300.415@silk.local \
    --to=fthain@telegraphics.com.au \
    --cc=debian-68k@lists.debian.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=stephen@marenka.net \
    /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