From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Borislav Petkov <bp@alien8.de>
Cc: Al Viro <viro@zeniv.linux.org.uk>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: 784d5699eddc ("x86: move exports to actual definitions")
Date: Tue, 18 Oct 2016 22:40:33 +0200 [thread overview]
Message-ID: <20161018204033.GB307@x4> (raw)
In-Reply-To: <20161018202915.GA307@x4>
On 2016.10.18 at 22:29 +0200, Markus Trippelsdorf wrote:
> On 2016.10.18 at 22:23 +0200, Borislav Petkov wrote:
> > Hey Al,
> >
> > I see the gazillion warnings below when building -rc1 here.
> >
> > When I revert
> >
> > 784d5699eddc ("x86: move exports to actual definitions")
> >
> > the warnings are gone.
>
> I'm seeing the same thing on ppc64le with an allmodconfig.
Also ld.gold doesn't handle linker scripts with empty archives.
It hits an internal error, see:
https://sourceware.org/bugzilla/show_bug.cgi?id=20693
--
Markus
next prev parent reply other threads:[~2016-10-18 20:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 20:23 784d5699eddc ("x86: move exports to actual definitions") Borislav Petkov
2016-10-18 20:29 ` Markus Trippelsdorf
2016-10-18 20:40 ` Markus Trippelsdorf [this message]
2016-10-19 0:10 ` Adam Borowski
2016-10-19 10:23 ` Borislav Petkov
2016-10-19 13:45 ` Steven Rostedt
2016-10-20 21:07 ` Gabriel C
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=20161018204033.GB307@x4 \
--to=markus@trippelsdorf.de \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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