On Wed, 4 Feb 2004, Charles Wilson wrote: > This is thanks to the new iconv support in newlib. Even tho it is > "turned off" in cygwin-1.5.7, the new cygwin package still installs its > own version of /usr/include/iconv.h -- and the "new" version is not, of > course, recognized as GNU iconv. > > Short-term solution: reinstall 'libiconv' > > Medium-term solution: next cygwin release, if it still does not use > newlib's iconv, should also _not_ include newlib's iconv.h
There's also libiberty.a, which gets install by cygwin and binutils, but I think it never caused any problems. It did for me on Linux and others when we compiled ksymoops (it was also part of gcc). Now I only install the binutils file. > Long-term solution: we really really need a package linter that detects > file conflicts like these BEFORE they lead to wierd problems. Any > volunteers? -- How to contact me - http://www.pervalidus.net/contact.html -- 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/
