My apologies for trusting ./configure to know what it is testing. So I suppose the real questions is why does ./configure complain about the libiconv that cygwin has. The following was produced by running ./configure
> checking whether the iconv installation is complete enough... no > > wv2 depends on a modern iconv installation, supporting UNICODELITTLE > and > UNICODEBIG. The detected iconv version doesn't support these > conversions. > > Please get a new libiconv from http://www.gnu.org/software/libiconv/ I suppose I will figure some way to work around ./configure to make it ignore its incorrect test. That won't help anything else that uses autoconf and tests for recent libiconv support. neal __________________________________________________ Do you Yahoo!? Yahoo! Shopping - Send Flowers for Valentine's Day http://shopping.yahoo.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
