From: Tony Breeds <tony@bakeyournoodle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Feng Tang <feng.tang@intel.com>
Subject: Re: linux-next: Tree for October 13
Date: Thu, 14 Oct 2010 13:55:26 +1100 [thread overview]
Message-ID: <20101014025526.GD24185@ozlabs.org> (raw)
In-Reply-To: <20101013174740.f48e4ec2.akpm@linux-foundation.org>
On Wed, Oct 13, 2010 at 05:47:40PM -0700, Andrew Morton wrote:
> gcc-4.1.0. Which is actually an officially banned compiler version:
>
> # if __GNUC_MINOR__ == 1 && __GNUC_PATCHLEVEL__ <= 1
> # error Your version of gcc miscompiles the __weak directive
>
> lazyass here needs to find a new cross-compiler.
*cough*
http://kernel.org/pub/tools/crosstool/files/bin/
If there are problems let me know.
Yours Tony
next prev parent reply other threads:[~2010-10-14 2:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 4:45 linux-next: Tree for October 13 Stephen Rothwell
2010-10-13 16:38 ` linux-next: Tree for October 13 (net/3c59x) Randy Dunlap
2010-10-13 16:54 ` David Miller
2010-10-13 16:41 ` linux-next: Tree for October 13 (staging/iio) Randy Dunlap
2010-10-13 19:07 ` Hennerich, Michael
2010-10-13 19:07 ` Hennerich, Michael
2010-10-14 10:21 ` Jonathan Cameron
2010-10-13 19:57 ` [PATCH -next] gpu/drm: fix build errors and kconfig dependency warnings Randy Dunlap
2010-10-14 0:38 ` linux-next: Tree for October 13 Andrew Morton
2010-10-14 0:41 ` H. Peter Anvin
2010-10-14 0:47 ` Andrew Morton
2010-10-14 2:55 ` Tony Breeds [this message]
2010-10-14 9:41 ` Feng Tang
-- strict thread matches above, loose matches on Subject: below --
2009-10-13 5:23 Stephen Rothwell
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=20101014025526.GD24185@ozlabs.org \
--to=tony@bakeyournoodle.com \
--cc=akpm@linux-foundation.org \
--cc=feng.tang@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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.