Date: Thu, 23 Feb 2012 13:22:26 -0500 (EST) From: Garrett Wollman <wollman@hergotha.csail.mit.edu> To: des@des.no Cc: arch@freebsd.org Subject: Re: bsd/citrus iconv Message-ID: <201202231822.q1NIMQOd020804@hergotha.csail.mit.edu> In-Reply-To: <86r4xl8lw0.fsf@ds4.des.no> 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> <20120223170918.GA79013@zim.MIT.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <86r4xl8lw0.fsf@ds4.des.no>, des@des.no writes: >It's a question of semantics... it's an extension (part of the >_XOPEN_UNIX option group), but if supported, it's supposed to be part of >libc. I don't think the SUS states this explicitly, but it's implied by >the lack of mention of a separate iconv library in the c99 man page. POSIX doesn't specify libc or any other library. It specifies (by omission) that the function shall be available when the "c99" command is used without any special "-l" arguments (such as "-l rt"). It can be located in any library, so long as "c99" always includes that library when building an executable. (Of course, we don't support _XOPEN_UNIX and probably never will, but that would be the requirement if we did.) -GAWollman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201202231822.q1NIMQOd020804>