From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, Anton Blanchard <anton@samba.org>
Subject: Re: linux-next: build failure after merge of the final tree (powerpc tree related)
Date: Fri, 3 Dec 2010 17:08:05 +1100 [thread overview]
Message-ID: <20101203170805.2d99f70c.sfr@canb.auug.org.au> (raw)
In-Reply-To: <1291355998.32570.417.camel@pasglop>
[-- Attachment #1: Type: text/plain, Size: 434 bytes --]
On Fri, 03 Dec 2010 16:59:58 +1100 Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
> This toolchain is a bit ancient I suppose... Anton, do you reckon we
> should use .long based macros for these for the time being or just
> require a newer binutils ?
The currently documented minimum binutils is 2.12 ...
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2010-12-03 6:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 5:32 linux-next: build failure after merge of the final tree (powerpc tree related) Stephen Rothwell
2010-12-03 5:59 ` Benjamin Herrenschmidt
2010-12-03 6:08 ` Stephen Rothwell [this message]
2010-12-03 11:26 ` Josh Boyer
2011-03-14 9:38 Stephen Rothwell
2011-03-14 20:37 ` Benjamin Herrenschmidt
2011-03-14 20:51 ` David Miller
2011-03-14 21:17 ` Thomas Gleixner
2011-03-14 21:21 ` Lennert Buytenhek
2011-05-05 3:41 Stephen Rothwell
2011-06-30 6:36 Stephen Rothwell
2011-06-30 7:09 ` Benjamin Herrenschmidt
2012-09-06 7:11 Stephen Rothwell
2012-09-06 8:20 ` Ananth N Mavinakayanahalli
2013-01-11 5:52 Stephen Rothwell
2013-01-11 6:04 ` Michael Neuling
2013-12-09 6:32 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=20101203170805.2d99f70c.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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 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).