All of lore.kernel.org
 help / color / mirror / Atom feed
From: Finn Thain <fthain@telegraphics.com.au>
To: debian-68k@lists.debian.org
Cc: linux-m68k@vger.kernel.org
Subject: Re: toolchain
Date: Sun, 6 Sep 2009 15:20:05 +1000 (EST)	[thread overview]
Message-ID: <alpine.OSX.2.00.0909061510270.415@silk.local> (raw)
In-Reply-To: <4AA2684E.1080009@codesourcery.com>



On Sat, 5 Sep 2009, Maxim Kuvyrkov wrote:

> > 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@.

Stephen, this patch will be needed in order to build glibc with TLS, since 
it provides the userspace headers for TLS.

http://marc.info/?l=linux-m68k&m=125145669021517&w=2

Not sure how debian handles the kernel headers. I presume that 
linux-libc-dev (probably 2.6.30) needs the patch? (As will the other 
kernel packages of course.)

Finn

  parent reply	other threads:[~2009-09-06  5:20 UTC|newest]

Thread overview: 53+ 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
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               ` Finn Thain [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2015-11-24 10:50 Toolchain Virgilia  Eigner
2014-03-03  1:58 Toolchain Michael Gloff
2014-03-03 18:52 ` Toolchain Paul Eggleton
2014-03-05 17:00   ` Toolchain Michael Gloff
2014-03-05 17:45     ` Toolchain Paul Eggleton
2014-03-05 19:56       ` Toolchain Michael Gloff
2014-03-05 21:14     ` Toolchain Khem Raj
2014-03-06 12:57       ` Toolchain Paul Barker
2014-01-03 16:46 toolchain Edward Vidal
2014-01-03 22:48 ` toolchain Philip Balister
2014-01-03 23:00   ` toolchain Gary Thomas
2008-07-03 14:17 qt4x11 vs. uicmoc4-native vs. qmake2-native Geoffrey Wossum
2008-07-04  6:54 ` Toolchain Stefano Regno
2008-07-04 12:56   ` Toolchain Leon Woestenberg
2008-07-23 15:09     ` Toolchain Stefano Regno

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.0909061510270.415@silk.local \
    --to=fthain@telegraphics.com.au \
    --cc=debian-68k@lists.debian.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.