Re: [bug-libunistring] Assertion failure on Cygwin

[Bruno Haible]

Hi Ludovic,

> > What does "patching sources" mean? Where are the patches that are being 
> > applied?
> 
> None
> 
> > What does "fixing libtool script" do? libunistring's embedded libtool 
> > script is
> > known to work fine on Cygwin 1.5.x.
> 
> It does this:
> 
> --8<---------------cut here---------------start------------->8---
> fixLibtool() {
>     sed 's^eval sys_lib_.*search_path=.*^^' < $1 > $1.tmp
>     mv $1.tmp $1
> }
> --8<---------------cut here---------------end--------------->8---
> 
> This is needed on NixOS, where “standard” search paths (/lib, /usr/lib,
> etc.) don’t exist.

Thanks for the precisions. This change is likely harmless.

> > Last not least, which version of cygwin are you using (show the result of
> > "uname -a")? 1.5.x or 1.7-beta?
> 
> It’s 1.5.25.

OK, that looks reasonable. Taking a closer look at your log file, I see this:

  configure flags: --disable-static --disable-dependency-tracking 
--prefix=/nix/store/z6b2k0lklh3340jm8dfvr054l4iqvhyd-libunistring-0.9.1  

(note the absence of a --with-libiconv-prefix option) and then this:

  checking iconv.h usability... no
  checking iconv.h presence... no
  checking for iconv.h... no

So, you are ignoring the list of dependencies listed in the DEPENDENCIES file,
and really building without any iconv() implementation being available. This
cannot work.

It is for distros (Linux distributors and packagers like DarwinPorts or NixOS)
that I added this DEPENDENCIES file and mentioned it right at the beginning of
the INSTALL file. The "./configure --help" output also mentions the
--with-libiconv-prefix option. I cannot help but wonder why the relevant
documentation is ignored.

Btw, I recommend the current version of libunistring, which is 0.9.1.1.

Bruno