From: "sam at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libelf/30729] elf_scncnt: undefined version: ELFUTILS_1.0 during linking phase of libelf.so
Date: Sun, 06 Aug 2023 23:48:26 +0000 [thread overview]
Message-ID: <bug-30729-10460-PGdZ88E4jG@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30729-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30729
Sam James <sam at gentoo dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sam at gentoo dot org
--- Comment #1 from Sam James <sam at gentoo dot org> ---
(In reply to Kostadin Shishmanov from comment #0)
> Steps to reproduce:
>
> 1. autoreconf -vfi
> 2. ./configure --enable-maintainer-mode --disable-debuginfod
> 3. export LDFLAGS="-Wl,--no-undefined-version"
> 4. make
>
To be clear, the reason that this is an interesting flag (and why OP is testing
this) is because LLD 16 made it default for a bit (then reverted it) and LLD 17
will be setting it too.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-08-06 23:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-06 18:13 [Bug libelf/30729] New: " kocelfc at tutanota dot com
2023-08-06 23:48 ` sam at gentoo dot org [this message]
2023-08-28 15:35 ` [Bug libelf/30729] Build failure with upcoming LLD 17 (elf_scncnt: undefined version: ELFUTILS_1.0 during linking phase of libelf.so) sam at gentoo dot org
2023-08-28 15:35 ` sam at gentoo dot org
2023-08-28 16:10 ` mark at klomp dot org
2023-08-28 16:26 ` kocelfc at tutanota dot com
2023-08-28 18:35 ` mark at klomp dot org
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=bug-30729-10460-PGdZ88E4jG@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.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).