From: Florian Weimer <fweimer@redhat.com>
To: "Andreas K. Huettel" <dilfridge@gentoo.org>
Cc: libc-alpha@sourceware.org
Subject: Re: libcidn
Date: Thu, 05 Oct 2017 13:40:00 -0000 [thread overview]
Message-ID: <5449beb9-289e-720e-76f6-823d9dcd3187@redhat.com> (raw)
In-Reply-To: <1745056.Yiv6T0xlHe@porto>
On 10/05/2017 03:16 PM, Andreas K. Huettel wrote:
> Mostly out of curiosity, what is the usecase for the glibc-internal libidn?
It's used by getaddrinfo if the AI_IDN flag is passed.
> A quick scan on my laptop (Gentoo Linux) shows no binaries that have
> libcidn.so in NEEDED (but many with the separate libidn.so).
It's not linked directly. getaddrinfo loads it on demand. It's this
way because no one has changed it yet (I tried, but got sidetracked by
dynamic linker issues). We should rewrite the code so that it tries
(external) libidn2 first, then (external) libidn, and then bails out,
and remove the actual IDN code from the library. Some care is necessary
because we should switch from dlsym to dlvsym for the lookup, for
forwards compatibility.
Thanks,
Florian
next prev parent reply other threads:[~2017-10-05 13:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 17:49 Remove add-ons mechanism Joseph Myers
2017-09-28 22:01 ` Zack Weinberg
2017-09-28 22:38 ` Joseph Myers
2017-09-29 11:04 ` Florian Weimer
2017-09-30 6:35 ` Florian Weimer
2017-09-30 21:42 ` Joseph Myers
2017-10-05 10:39 ` Andreas K. Huettel
2017-10-05 11:07 ` Florian Weimer
2017-10-05 12:54 ` Joseph Myers
2017-10-05 13:16 ` libcidn (was: Re: Remove add-ons mechanism) Andreas K. Huettel
2017-10-05 13:39 ` libcidn Andreas Schwab
2017-10-05 13:40 ` Florian Weimer [this message]
2017-10-05 21:11 ` Remove add-ons mechanism Andreas K. Huettel
2017-10-05 21:30 ` Joseph Myers
2017-10-05 15:59 ` Joseph Myers
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=5449beb9-289e-720e-76f6-823d9dcd3187@redhat.com \
--to=fweimer@redhat.com \
--cc=dilfridge@gentoo.org \
--cc=libc-alpha@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).