wv2 under cygwin (config issues)

  • Anonymous - 2003-02-17

    I managed to compile wv2 under cygwin but only after
    having to make changes to the configure script.

    configure claimed that the iconv support was not complete
    > checking whether the iconv installation is complete enough... no

    It turns out that the cygwin already has libiconv-1.8
    so the test for support was failing under cygwin.

    If I make the following change to wv2's configure, I can then make the package

    < 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 ...
      gcc -o conftest.exe -O2 -liconv conftest.c
    produces quite different results from
      gcc -o conftest.exe -O2 conftest.c -liconv
    which are the compile lines from the test being run by configure.

    How the original test works elsewhere but fails on cygwin
    is beyond me at this time.

    The response from the cygwin list was ...

    > I looked at wv2's configure.in.
    > They are wrongly putting -liconv into
    > $LDFLAGS, not $LIBS.
    > It's that gcc link order FAQ all over again.


    > Report the bug to wv2, then.
    > It is a trivial misuse of the
    > compiler, so should be easily fixed by them.


    So at least now I got wv2 complied under cygwin.
    Unfortunately I don't yet have wvWare running as it
    wasn't in the wv2 archive I downloaded.  I did try to
    configure the wv-0.6.5 but ran into the following ...

    >loading cache /dev/null within ltconfig
    >ltconfig: you must specify a host type if you use `--no-verify'
    >Try `ltconfig --help' for more information.
    >configure: error: libtool configure failed

    While there is a perfectly good libtool under cygwin
    there doesn't seem to be any ltconfig (or need of it)

    I will do some more investigation

    • Francis James Franklin

      well. perhaps I should point out that wv and wv2 are entirely separate packages, even though their stated aim is the same? or perhaps I shouldn't. no. okay.

      wvWare is part of wv, not wv2. The latest release is wv-0.7.4. wv doesn't use libtool, not unless you run autogen.sh, and if you do run autogen.sh there are no guarantees - it's not as fully tested.

      It may be worth your while getting the latest wv from AbiWord's CVS repository.


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks