Date: Fri, 17 Feb 2012 18:07:54 +0200 From: Andriy Gapon <avg@FreeBSD.org> To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= <des@des.no> Cc: Gabor Kovesdan <gabor@FreeBSD.org>, freebsd-arch@FreeBSD.org Subject: Re: bsd/citrus iconv Message-ID: <4F3E7B5A.20103@FreeBSD.org> In-Reply-To: <864nupcuvl.fsf@ds4.des.no> References: <4F3C28DD.1020003@FreeBSD.org> <4F3C2D2D.5000402@FreeBSD.org> <4F3E78BA.4060203@FreeBSD.org> <864nupcuvl.fsf@ds4.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
on 17/02/2012 18:00 Dag-Erling Smørgrav said the following: > Andriy Gapon <avg@FreeBSD.org> writes: >> Gabor Kovesdan <gabor@FreeBSD.org> writes: >>> Also, it is not really possible to avoid exposing it. >> ... I am not sure why. If we don't install any of its headers and install its >> library as e.g. libbsdiconv.so, then it's perfectly usable by the >> libraries/executables in the base system that were specifically compiled to use >> this library and it's quite well hidden from the rest. > > It's not a separate library - if you enable it, it's compiled into libc. But nothing precludes it from being a separate library in principle? There is even src/lib/libiconv, it's just not connected to the build. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F3E7B5A.20103>