Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 23 Feb 2012 12:09:18 -0500
From:      David Schultz <das@FreeBSD.ORG>
To:        Gabor Kovesdan <gabor@FreeBSD.ORG>
Cc:        Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= <des@des.no>, Andriy Gapon <avg@FreeBSD.ORG>, freebsd-arch@FreeBSD.ORG
Subject:   Re: bsd/citrus iconv
Message-ID:  <20120223170918.GA79013@zim.MIT.EDU>
In-Reply-To: <4F3EADB5.7060008@FreeBSD.org>
References:  <4F3C28DD.1020003@FreeBSD.org> <4F3C2D2D.5000402@FreeBSD.org> <4F3E78BA.4060203@FreeBSD.org> <864nupcuvl.fsf@ds4.des.no> <4F3E7B5A.20103@FreeBSD.org> <86zkchbff6.fsf@ds4.des.no> <4F3EADB5.7060008@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Feb 17, 2012, Gabor Kovesdan wrote:
> Em 17-02-2012 17:19, Dag-Erling Smørgrav escreveu:
> >Andriy Gapon<avg@FreeBSD.org>  writes:
> >>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.
> >You're right - for some reason, I thought src/lib/libiconv was just a
> >Makefile for GNU libiconv.
> POSIX requires iconv() to be in libc. However, a glue Makefile was 
> provided there for testing purposes.

Where do you see that?  I believe it's optional.  Providing it as
a separate library is more maintainable, and makes it easier for
people to drop in a different iconv library if they need it.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120223170918.GA79013>