public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jan at jankratochvil dot net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/30878] Alpine Linux: libinproctrace: undefined reference to libintl_gettext
Date: Mon, 25 Sep 2023 03:05:11 +0000 [thread overview]
Message-ID: <bug-30878-4717-VLcfMxhsCE@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30878-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30878
Jan Kratochvil <jan at jankratochvil dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jan at jankratochvil dot net
--- Comment #2 from Jan Kratochvil <jan at jankratochvil dot net> ---
If there is anything missing in the OS and there is an option to disable it the
configure script should detect such missing OS feature and disable it on its
own. I did not enforce --enable-nls, in such case it should correctly fail.
I see now binutils/README does describe it:
Native Language Support
=======================
By default Native Language Support will be enabled for binutils. On
some systems however this support is not present and can lead to error
messages such as "undefined reference to `libintl_gettext'" when
building there tools. If that happens the NLS support can be disabled
by adding the --disable-nls switch to the configure line like this:
../binutils-XXX/configure --disable-nls
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-09-25 3:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 14:11 [Bug build/30878] New: " jan at jankratochvil dot net
2023-09-25 2:50 ` [Bug build/30878] " lienze at sourceware dot org
2023-09-25 3:05 ` jan at jankratochvil dot net [this message]
2023-09-26 0:27 ` sam at gentoo dot org
2023-11-26 9:42 ` larserik at netix dot se
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-30878-4717-VLcfMxhsCE@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).