Dave Korn wrote:
> To elaborate: I'm building graphviz. Its configure correctly spotted we
> have no iconv_xxx functions in the library, so did not define HAVE_ICONV; the
> application the supplies its own dummy stubbed-out versions of the
> iconv_open/iconv/iconv_close functions, but although
On 11 February 2008 19:13, Reini Urban wrote:
> 2008/2/11, Dave Korn <[EMAIL PROTECTED]>:
>> Does anyone understand the difference between iconv_open and
>> libiconv_open, and why the libiconv package supplies a header that
>> declares only iconv_XXX and a library that defines only libiconv_
2008/2/11, Dave Korn <[EMAIL PROTECTED]>:
> Does anyone understand the difference between iconv_open and libiconv_open,
> and why the libiconv package supplies a header that declares only iconv_XXX
> and a library that defines only libiconv_? I find this confusing, and so
> does ./configure
Does anyone understand the difference between iconv_open and libiconv_open,
and why the libiconv package supplies a header that declares only iconv_XXX
and a library that defines only libiconv_? I find this confusing, and so
does ./configure and friends.
cheers,
DaveK
--
Can't
4 matches
Mail list logo
