From: Jan Beulich <jbeulich@suse.com>
To: "Andreas K. Hüttel" <dilfridge@gentoo.org>
Cc: toolchain@gentoo.org, binutils@sourceware.org
Subject: Re: [PATCH, needs more eyes] Relink also libopcodes and libgprofng to newly built libiberty.a
Date: Wed, 1 Mar 2023 09:29:13 +0100 [thread overview]
Message-ID: <0598a25f-8610-25e3-45ae-dc0e77852761@suse.com> (raw)
In-Reply-To: <20230228224937.3832887-1-dilfridge@gentoo.org>
On 28.02.2023 23:49, Andreas K. Hüttel via Binutils wrote:
> For Gentoo users, after updating gcc, a subsequent build of
> binutils can fail during "make install" with the following symptoms:
>
> lto1: fatal error: bytecode stream in file '/usr/lib64/binutils/x86_64-pc-linux-gnu/2.37_p1/libiberty.a' generated with LTO version 11.0 instead of the expected 11.2
> compilation terminated.
>
> The relink command picks up the installed version of libiberty.a
> instead of the just built one. This commit addresses the issue by
> replicating the workaround made in 7d53105d for libctf also for
> libopcodes and libgprofng.
>
> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29042
> Bug: https://bugs.gentoo.org/834720
> Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
Looks largely okay to me, but please add comments along the lines of the
one found in libctf/Makefile.am.
I'm not going to ask ...
> ---
> gprofng/src/Makefile.am | 3 ++-
> gprofng/src/Makefile.in | 3 ++-
> opcodes/configure | 4 ++--
> opcodes/configure.ac | 4 ++--
> 4 files changed, 8 insertions(+), 6 deletions(-)
... why libopcodes handles this in configure rather than in Makefile, as
that's a pre-existing (apparent) oddity.
Jan
next prev parent reply other threads:[~2023-03-01 8:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 22:49 Andreas K. Hüttel
2023-03-01 8:29 ` Jan Beulich [this message]
2023-03-01 22:17 ` Vladimir Mezentsev
2023-03-02 5:11 ` Alan Modra
2023-03-02 8:10 ` Vladimir Mezentsev
2023-03-02 9:27 ` Alan Modra
2023-03-15 20:51 ` Andreas K. Huettel
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=0598a25f-8610-25e3-45ae-dc0e77852761@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=dilfridge@gentoo.org \
--cc=toolchain@gentoo.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 read-only IMAP folder(s) and NNTP newsgroup(s).