iconv vs. libiconv confusion
Brian Dessent
brian@dessent.net
Tue Feb 12 04:43:00 GMT 2008
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 those functions don't
> exist they /are/ prototyped in the header file and hence the build fails
> because the dummy versions don't have quite the same prototypes as the
> non-existing ones declared in the header file.
I ran into eactly this problem recently. The issue is that you
accidently overwrote the libiconv header with the newlib header of the
same name (iconv.h). You get that if you a make install (or whatever)
for newlib to get updates headers. The newlib one doesn't work
obviously because it simply defines iconv_open. The proper libiconv
header works correctly.
Brian
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
More information about the Cygwin
mailing list