From: Theodore Tso <tytso@MIT.EDU>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Tom Rini <trini@kernel.crashing.org>,
torvalds@linux-foundation.org, bunk@kernel.org,
venkatesh.pallipadi@intel.com, davem@davemloft.net,
mingo@elte.hu, tglx@linutronix.de, hpa@zytor.com,
linux-kernel@vger.kernel.org, suresh.b.siddha@intel.com
Subject: Re: huge gcc 4.1.{0,1} __weak problem
Date: Fri, 2 May 2008 09:43:49 -0400 [thread overview]
Message-ID: <20080502134349.GI17365@mit.edu> (raw)
In-Reply-To: <19f34abd0805020018i11fb722fg5a4cc180ab5f2856@mail.gmail.com>
On Fri, May 02, 2008 at 09:18:10AM +0200, Vegard Nossum wrote:
> though these are largely untested with Linux Kernel. Most of them are
> gcc 3.4.5 (this should in theory compile the kernel correctly), though
> I found an e-mail from Ingo saying that you need the -tls versions for
> stackprotector to work correctly. This might be a good time to ask if
> I should be making gcc 4.1.2s instead. I need to recompile in either
> case.
Out of curiosity, are you using the stock gcc/binutils from the FSF,
or one of the distro toolchains? When we were investigating which
compiler/toolchain to use for the LSB Sample Implementation, one of
the comments that I got from folks like Eric Troan from rPath and
others was that out-of-the-box compiler/toolchain had so many bugs,
particularly on non-x86 architectures, that they found they were much
better off using a distro-patched/bug-fixed compiler/toolchain and
treating that as the upstream.
There has been some requests to include cross-compilation
functionality into the LSB Build Environment, so I'd be interested in
seeing how your work has been going, and maybe there's some
opportunity to work together. Is there a mailing list you have for
this project?
- Ted
next prev parent reply other threads:[~2008-05-02 13:45 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 1:31 [PATCH] /dev/mem gcc weak function workaround Venki Pallipadi
2008-04-30 4:28 ` David Miller
2008-04-30 12:49 ` Pallipadi, Venkatesh
2008-04-30 20:15 ` Tom Rini
2008-05-01 21:56 ` huge gcc 4.1.{0,1} __weak problem Adrian Bunk
2008-05-01 22:20 ` Andrew Morton
2008-05-01 22:27 ` Linus Torvalds
2008-05-01 22:33 ` Andrew Morton
2008-05-01 23:24 ` Tom Rini
2008-05-01 23:59 ` Andrew Morton
2008-05-02 0:21 ` Justin Mattock
2008-05-02 7:18 ` Vegard Nossum
2008-05-02 13:43 ` Theodore Tso [this message]
2008-05-02 8:10 ` Adrian Bunk
2008-05-02 9:09 ` Andi Kleen
2008-05-01 22:35 ` Venki Pallipadi
2008-05-01 22:42 ` Andrew Morton
2008-05-01 22:49 ` Jakub Jelinek
2008-05-01 23:21 ` Tom Rini
2008-05-01 23:30 ` Venki Pallipadi
2008-05-02 0:34 ` Linus Torvalds
2008-05-02 0:39 ` Suresh Siddha
2008-05-02 21:11 ` Jeremy Fitzhardinge
2008-05-02 22:02 ` David Miller
2008-05-01 23:23 ` Tom Rini
2008-05-01 22:51 ` David Miller
2008-06-26 10:37 ` [2.6.26 patch] #error for gcc 4.1.{0,1} Adrian Bunk
2008-05-02 21:09 ` huge gcc 4.1.{0,1} __weak problem Jeremy Fitzhardinge
2008-05-02 21:19 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2008-05-01 23:55 Chris Knadle
2008-05-02 9:19 ` Miquel van Smoorenburg
2008-05-02 9:55 ` Alistair John Strachan
2008-05-02 10:43 ` Sam Ravnborg
2008-05-02 11:48 ` Alistair John Strachan
2008-05-02 13:57 ` Sam Ravnborg
2008-05-02 14:11 ` Jakub Jelinek
2008-05-02 15:26 ` Alistair John Strachan
2008-05-02 14:57 ` Jeremy Fitzhardinge
2008-05-02 12:40 ` Sven-Haegar Koch
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=20080502134349.GI17365@mit.edu \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=trini@kernel.crashing.org \
--cc=vegard.nossum@gmail.com \
--cc=venkatesh.pallipadi@intel.com \
/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