bsd/citrus iconv

[Tim Kientzle]

On Mar 2, 2012, at 9:16 AM, David Schultz wrote:

> On Thu, Feb 23, 2012, Dag-Erling Sm?rgrav wrote:
>> Garrett Wollman <wollman at 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.

Tim