This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: libcidn

From: Andreas Schwab <schwab at suse dot de>
To: "Andreas K. Huettel" <dilfridge at gentoo dot org>
Cc: libc-alpha at sourceware dot org
Date: Thu, 05 Oct 2017 15:39:04 +0200
Subject: Re: libcidn
Authentication-results: sourceware.org; auth=none
References: <alpine.DEB.2.20.1709281748010.30081@digraph.polyomino.org.uk> <d079cb89-4f6d-31a1-623e-277383d8fe3a@redhat.com> <alpine.DEB.2.20.1710051253180.18935@digraph.polyomino.org.uk> <1745056.Yiv6T0xlHe@porto>

On Okt 05 2017, "Andreas K. Huettel" <dilfridge@gentoo.org> wrote:

> Mostly out of curiosity, what is the usecase for the glibc-internal libidn?

It is used by the resolver for IDN.

> 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 loaded on demand, see libidn/idn-stub.c.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

References:
- Re: Remove add-ons mechanism
  - From: Florian Weimer
- Re: Remove add-ons mechanism
  - From: Joseph Myers
- libcidn (was: Re: Remove add-ons mechanism)
  - From: Andreas K. Huettel

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]