Re: wvWare and cygwin

2003-02-13 Thread Max Bowsher
Christopher Faylor wrote: > On Thu, Feb 13, 2003 at 12:43:49PM -0800, neal somos wrote: >> If I make the following change to wv2's configure, I can then make >> the package >> >> 25826c25826 >> < ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS >> conftest.$ac_ext $LIBS >&5' >> --- >>>

Re: wvWare and cygwin

2003-02-13 Thread Max Bowsher
From: "neal somos" <[EMAIL PROTECTED]> > If I make the following change to wv2's configure, I can then make the package > > 25826c25826 > < ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5' > --- > > ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS confte

Re: wvWare and cygwin

2003-02-13 Thread Christopher Faylor
On Thu, Feb 13, 2003 at 03:48:54PM -0500, Christopher Faylor wrote: >On Thu, Feb 13, 2003 at 12:43:49PM -0800, neal somos wrote: >>If I make the following change to wv2's configure, I can then make the package >> >>25826c25826 >>< ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS confte

Re: wvWare and cygwin

2003-02-13 Thread Christopher Faylor
On Thu, Feb 13, 2003 at 12:43:49PM -0800, neal somos wrote: >If I make the following change to wv2's configure, I can then make the package > >25826c25826 >< ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext >$LIBS >&5' >--- >> ac_link='$CC -o conftest$ac_exeext $CFLAG

Re: wvWare and cygwin

2003-02-13 Thread neal somos
If I make the following change to wv2's configure, I can then make the package 25826c25826 < ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5' --- > ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS conftest.$ac_ext $LDFLAGS $LIBS >>&5' Basically ...

Re: wvWare and cygwin

2003-02-13 Thread Max Bowsher
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 complet

Re: wvWare and cygwin

2003-02-13 Thread neal somos
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 dep

Re: wvWare and cygwin

2003-02-12 Thread Max Bowsher
neal somos wrote: > So I wanted to use the 'wv' tools from http://www.wvware.com/ > and downloaded the most recent 'wv2' files. > > When running ./configure on wv2 I get the following ... > > --- > checking for iconv... no > checking for libiconv_open in -liconv... yes > checkin

Re: wvWare and cygwin

2003-02-12 Thread David Huang
neal somos wrote: Then when I download the latest libiconv-1.8 run ./configure and then 'make' I get the following --- builddir="`pwd`"; cd libcharset && make all && make install-lib libdir="$builddir/lib" includedir="$builddir/lib" make[1]: Entering directory `/home/nas0426/