Date: Fri, 2 Mar 2012 21:25:32 -0800 From: Tim Kientzle <tim@kientzle.com> To: David Schultz <das@freebsd.org> Cc: =?iso-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no>, Garrett Wollman <wollman@hergotha.csail.mit.edu>, arch@freebsd.org Subject: Re: bsd/citrus iconv Message-ID: <B1CA3621-0760-4A2D-BF52-F12DA2164810@kientzle.com> In-Reply-To: <20120302171647.GA29850@zim.MIT.EDU> References: <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> <201202231822.q1NIMQOd020804@hergotha.csail.mit.edu> <201202231926.q1NJQPFa021654@hergotha.csail.mit.edu> <86d3958cqi.fsf@ds4.des.no> <20120302171647.GA29850@zim.MIT.EDU>
index | next in thread | previous in thread | raw e-mail
On Mar 2, 2012, at 9:16 AM, David Schultz wrote: > On Thu, Feb 23, 2012, Dag-Erling Sm?rgrav wrote: >> Garrett Wollman <wollman@hergotha.csail.mit.edu> writes: >>> You missed the bit on the next page: >>> >>> It is unspecified whether the libraries libc.a, libm.a, >>> librt.a, libpthread.a, libl.a, liby.a, or libxnet exist as >>> regular files. The implementation may accept as -l operands >>> names of objects that do not exist as regular files. >> >> That's entirely academic unless you want to modify gcc and clang to >> automatically pull in libiconv. The point is that if the iconv >> extension is implemented, it must be available without requiring >> additional -l options. > > If the linker included libiconv automatically, would it be > possible to switch iconv implementations without recompiling, by > using libmap.conf? Or is the ABI (e.g., type of iconv_t) > incompatible? …. Very incompatible. The functions actually have different names in the library. So switching implementations via library mapping is not going to work. Timhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B1CA3621-0760-4A2D-BF52-F12DA2164810>