bug-libunistring
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-libunistring] Assertion failure on Cygwin


From: Ludovic Courtès
Subject: Re: [bug-libunistring] Assertion failure on Cygwin
Date: Fri, 18 Sep 2009 19:54:35 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)

Hi,

Bruno Haible <address@hidden> writes:

[...]

> 22 test failures in total. This build is not usable.
>
>> See http://hydra.nixos.org/build/74591 for details.
>
> The log file at http://hydra.nixos.org/build/74591/log contains the lines:
>
>   patching sources
>   configuring
>   fixing libtool script ./build-aux/ltmain.sh
>
> What does "patching sources" mean? Where are the patches that are being 
> applied?

None (see
https://svn.nixos.org/repos/nix/nixpkgs/trunk/pkgs/development/libraries/libunistring/default.nix).
This message is misleading: when patches are actually applied, there are
additional messages saying “applying ‘foo.patch’”.

> 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.

> 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.  I don't have direct access to the machine, though, only
via NixOS' build farm.

Thanks,
Ludo'.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]