Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Stephen Casner <casner@acm.org>
To: Nick Alcock <nick.alcock@oracle.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: new gdb build failures on MacOS X (... fallout from libintl fixups, see users/nalcock/included-gettext)
Date: Thu, 4 Feb 2021 12:43:29 -0800 (PST)	[thread overview]
Message-ID: <alpine.OSX.2.21.9999.2102041238500.86462@auge.attlocal.net> (raw)
In-Reply-To: <87k0rna7w4.fsf_-_@esperi.org.uk>

On Thu, 4 Feb 2021, Nick Alcock wrote:
> On 4 Feb 2021, Stephen Casner told this:
> > the gdb link fails with these undefined symbols:
> >
> >   "_iconv", referenced from:
> >       __nl_find_msg in libintl.a(dcigettext.o)
> >   "_iconv_close", referenced from:
> >       __nl_free_domain_conv in libintl.a(loadmsgcat.o)
> >   "_iconv_open", referenced from:
> >       __nl_init_domain_conv in libintl.a(loadmsgcat.o)
>
> Now *this* is probably, er... well, I'm not sure it's my fault because I
> didn't touch gdb, only gdbserver and intl/ itself (in a way that
> shouldn't have affected the way gdb uses it), but it's certainly
> suboptimal.

An initial reply just to be clear: this is not a new problem caused by
your changes.  I have encountered since I began working on binutils
and gcc for pdp11 a year ago.

                                                        -- Steve

  reply	other threads:[~2021-02-04 20:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <874kird819.fsf@esperi.org.uk>
     [not found] ` <alpine.OSX.2.21.9999.2102041135350.86462@auge.attlocal.net>
2021-02-04 20:35   ` Nick Alcock via Gdb-patches
2021-02-04 20:43     ` Stephen Casner [this message]
2021-02-04 22:31       ` Nick Alcock via Gdb-patches
2021-02-04 21:40     ` Stephen Casner
2021-02-09 21:49     ` Andrew Burgess
2021-02-10 16:12       ` Christian Biesinger via Gdb-patches

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=alpine.OSX.2.21.9999.2102041238500.86462@auge.attlocal.net \
    --to=casner@acm.org \
    --cc=gdb-patches@sourceware.org \
    --cc=nick.alcock@oracle.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