LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Michael K. Edwards" <medwards.linux@gmail.com>
To: "Linux Kernel List" <linux-kernel@vger.kernel.org>,
	"Sam Ravnborg" <sam@ravnborg.org>,
	linux-arm-toolchain@lists.arm.linux.org.uk,
	linux-arm-kernel@lists.arm.linux.org.uk, crossgcc@sourceware.org
Subject: Re: More ARM binutils fuckage
Date: Tue, 5 Dec 2006 15:29:22 -0800	[thread overview]
Message-ID: <f2b55d220612051529t3c0dcda8ma920c13b00899b10@mail.gmail.com> (raw)
In-Reply-To: <20061205193357.GF24038@flint.arm.linux.org.uk>

On 12/5/06, Russell King <rmk+lkml@arm.linux.org.uk> wrote:
> There's not much to say about this, other than scream and go hide in the
> corner.  ARM toolchains are just basically fscked.

And while we're on the topic of ARM linux toolchain fsckage, it would
be nice to know what patches and incantations are currently
recommended when configuring gcc for building various modern ARM
kernel/ABI configurations (OABI + soft VFP, EABI, etc.).

There has been some discussion on the crossgcc mailing list,
especially around recent compilers and NPTL/TLS, and crosstool has
accumulated some of the relevant patches.  If an expert (i. e.,
someone who has built their own toolchain and gotten an ARM EABI/NPTL
system all the way up) were to reply to this message with some
details, we might be able to coax chip vendors off of hard-float
gcc-3.3/glibc-2.3.x/linuxthreads toolchains.

Cheers,
- Michael

  reply	other threads:[~2006-12-05 23:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-05 19:33 Russell King
2006-12-05 23:29 ` Michael K. Edwards [this message]
2006-12-06  0:22   ` Russell King
2006-12-06  1:08     ` Lennert Buytenhek
2006-12-06  6:43       ` Re[2]: " Paul Sokolovsky
2006-12-06  8:17         ` Koen Kooi
2006-12-06 14:37         ` Re[2]: " Bruce Ashfield
2006-12-06  1:34     ` Michael K. Edwards
2006-12-06  0:25 ` Russell King

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=f2b55d220612051529t3c0dcda8ma920c13b00899b10@mail.gmail.com \
    --to=medwards.linux@gmail.com \
    --cc=crossgcc@sourceware.org \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-arm-toolchain@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --subject='Re: More ARM binutils fuckage' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).