From: Andi Kleen <ak@linux.intel.com>
To: Jim Davis <jim.epost@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Randy Dunlap <rdunlap@infradead.org>,
linux-next <linux-next@vger.kernel.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Michal Marek <mmarek@suse.cz>
Subject: Re: linux-next: Tree for May 7 (argh)
Date: Thu, 8 May 2014 10:08:51 -0700 [thread overview]
Message-ID: <20140508170851.GU19657@tassilo.jf.intel.com> (raw)
In-Reply-To: <CA+r1ZhjErMWqVY5kSfMqLUAeQNMQhLXdwRMY2ro-OQMzbgEX9g@mail.gmail.com>
On Thu, May 08, 2014 at 10:05:35AM -0700, Jim Davis wrote:
> On 5/7/14, Andi Kleen <ak@linux.intel.com> wrote:
>
> > It sounds like it misdetects your binutils. LTO should
> > disable itself when your binutils cannot handle it. Can you send me
> > the full build log and output of ld --version and gcc --version
> > please?
>
> With next-20140518 I am getting
>
> buildlog-1399568101.txt:/home/jim/linux/scripts/Makefile.lto:76:
> "WARNING: Too old linker version 22400000 for kernel LTO. You need
> Linux binutils. CONFIG_LTO disabled."
Ok so LTO is not active, and you still get errors.
That is odd.
>
> I don't recall seeing that when the problems first started, but I
> didn't save a buildlog from back then...
Please send a full build log / config
-Andi
next prev parent reply other threads:[~2014-05-08 17:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 7:33 linux-next: Tree for May 7 Stephen Rothwell
2014-05-07 20:52 ` linux-next: Tree for May 7 (argh) Randy Dunlap
2014-05-07 21:45 ` Jim Davis
2014-05-07 22:02 ` Stephen Rothwell
2014-05-07 22:17 ` Jim Davis
2014-05-08 1:10 ` Andi Kleen
2014-05-08 16:54 ` Randy Dunlap
2014-05-08 17:05 ` Jim Davis
2014-05-08 17:08 ` Andi Kleen [this message]
2014-05-08 17:40 ` Jim Davis
2014-05-07 21:56 ` Stephen Rothwell
2014-05-07 22:31 ` Randy Dunlap
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=20140508170851.GU19657@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=jim.epost@gmail.com \
--cc=linux-next@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=rdunlap@infradead.org \
--cc=rusty@rustcorp.com.au \
--cc=sfr@canb.auug.org.au \
/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).