Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <016401c2d379$4959ca40$78d96f83@pomello> From: "Max Bowsher" To: "neal somos" , References: <20030213145932 DOT 69192 DOT qmail AT web12303 DOT mail DOT yahoo DOT com> Subject: Re: wvWare and cygwin Date: Thu, 13 Feb 2003 16:02:19 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 neal somos wrote: > 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. Umm... Why not fix the test? Max. -- 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/