From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Thiago Jung Bauermann <bauerman@linux.vnet.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Michael Ellerman <mpe@ellerman.id.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
PowerPC <linuxppc-dev@lists.ozlabs.org>
Subject: Re: linux-next: build failure after merge of the akpm-current tree
Date: Fri, 25 Nov 2016 10:43:12 +1100 [thread overview]
Message-ID: <20161125104312.6bc3fdaf@canb.auug.org.au> (raw)
In-Reply-To: <9443137.1vHEJqnA2s@morokweng>
Hi Thiago,
On Thu, 24 Nov 2016 13:02:39 -0200 Thiago Jung Bauermann <bauerman@linux.vnet.ibm.com> wrote:
>
> Am Donnerstag, 24. November 2016, 16:01:51 BRST schrieb Stephen Rothwell:
> > Hi Andrew,
> >
> > After merging the akpm-current tree, today's linux-next build (powerpc
> > ppc64_defconfig) failed like this:
> >
> > powerpc-linux-ld: unrecognized option '--no-dynamic-linker'
> >
> > Caused by patch
> >
> > "powerpc: add purgatory for kexec_file_load implementation"
> >
>
> Sorry about that. --no-dynamic-linker was added in binutils 2.26.
> The patch below fixes the problem.
OK, I will apply that patch instead of disabling CONFIG_KEXEC_FILE
today.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2016-11-24 23:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 5:01 linux-next: build failure after merge of the akpm-current tree Stephen Rothwell
2016-11-24 15:02 ` Thiago Jung Bauermann
2016-11-24 23:43 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-14 5:59 Stephen Rothwell
2016-05-02 8:32 Stephen Rothwell
2016-05-02 11:17 ` Aneesh Kumar K.V
2015-04-13 11:20 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=20161125104312.6bc3fdaf@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=bauerman@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.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).