From: Chris Packham via Gdb <gdb@sourceware.org>
To: GDB Mailing list <gdb@sourceware.org>
Subject: Re: gdbserver seems to have grown a dependency on libiconv
Date: Tue, 23 Jul 2024 13:57:03 +1200 [thread overview]
Message-ID: <CAFOYHZAwDNNmkKVyvWH3f5-acVMCe=w8_eVuvjKcL=Qy_Yq54g@mail.gmail.com> (raw)
In-Reply-To: <CAFOYHZBpoTdVwr2VPFAUWxALAgsyoxzV0Cf2C6egmoKGBwVfcQ@mail.gmail.com>
On Tue, Jul 23, 2024 at 1:43 PM Chris Packham <judge.packham@gmail.com> wrote:
>
> Hi,
>
> I'm just looking at adding gdb 15 to crosstool-ng. One configuration
> that's having problems is xtensa-fsf-linux-uclibc.
>
> [ERROR] configure: error: could not find libiconv (required for
> host xtensa-fsf-linux-uclibc)[ERROR] make[2]: *** [Makefile:10924:
> configure-gdbserver] Error 1
> [ERROR] make[2]: *** Waiting for unfinished jobs....
>
> I don't think it's anything to do with the specific architecture but
> it just happens this configuration doesn't end up building libiconv as
> a dependency for any other part of the toolchain.
>
> Is libiconv actually a requirement for gdbserver or is this something
> that has leaked through now that gdb and gdbserver share a lot of
> infrastructure?
Answering my own question. Commit 07b3255c3ba ("Filter invalid
encodings from Linux thread names") started using iconv in gdbserver
and commit da48217f315 ("gdbserver/linux: probe for libiconv in
configure") added the configure check. So this appears completely
intentional. I'll add something to crosstool-ng to make libiconv a
dependency for gdbserver.
>
> Thanks,
> Chris
prev parent reply other threads:[~2024-07-23 1:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 1:43 Chris Packham via Gdb
2024-07-23 1:57 ` Chris Packham via Gdb [this message]
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='CAFOYHZAwDNNmkKVyvWH3f5-acVMCe=w8_eVuvjKcL=Qy_Yq54g@mail.gmail.com' \
--to=gdb@sourceware.org \
--cc=judge.packham@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox