From: Alan Modra <amodra@gmail.com>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: kbuild test robot <fengguang.wu@intel.com>,
kbuild-all@01.org, linux-kbuild@vger.kernel.org,
Masahiro Yamada <yamada.masahiro@socionext.com>
Subject: Re: [kbuild:thin-ar 5/8] ia64-linux-ld: warning: .note.gnu.build-id section discarded, --build-id ignored.
Date: Thu, 22 Jun 2017 23:34:01 +0930 [thread overview]
Message-ID: <20170622140400.GE8406@bubble.grove.modra.org> (raw)
In-Reply-To: <20170622143327.32177b0a@roar.ozlabs.ibm.com>
On Thu, Jun 22, 2017 at 02:33:27PM +1000, Nicholas Piggin wrote:
> On Thu, 22 Jun 2017 11:48:38 +0800
> kbuild test robot <fengguang.wu@intel.com> wrote:
> > >> ia64-linux-ld: warning: .note.gnu.build-id section discarded, --build-id ignored.
>
>
> Sigh.
>
> What's happening here is that when performing the final link with the
> -R option, the linker forgets to emit the --build-id section it was
> asked to.
>
> This is the final link command line that causes the error:
>
> $ ia64-linux-ld -static -R arch/ia64/kernel/gate-syms.o --build-id -o vmlinux -T ./arch/ia64/kernel/vmlinux.lds --whole-archive built-in.o --no-whole-archive --start-group lib/lib.a arch/ia64/lib/lib.a --end-group
Try putting the --just-symbols (-R) file after --no-whole-archive.
The idea being to make it not the first object file. --just-symbols
files have their contents discarded, and the linker is stupidly
attaching the section it creates to hold the build-id, to that file.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2017-06-22 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 3:48 [kbuild:thin-ar 5/8] ia64-linux-ld: warning: .note.gnu.build-id section discarded, --build-id ignored kbuild test robot
2017-06-22 4:33 ` Nicholas Piggin
2017-06-22 5:42 ` Nicholas Piggin
2017-06-22 14:04 ` Alan Modra [this message]
2017-06-22 14:23 ` Nicholas Piggin
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=20170622140400.GE8406@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=yamada.masahiro@socionext.com \
/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.