On 2016-02-22 12:44, Pavel Raiskup wrote: > Hi Daniel, > > On Saturday 20 of February 2016 14:29:47 Daniel Kahn Gillmor wrote: >> Over on https://bugs.debian.org/814951, Werner Koch and i are discussing >> how https://debbugs.gnu.org/13414 is still a problem with libtool. In >> particular, GNU libtool can't seem to detect that a .def file is valid >> unless EXPORT is the literal first line in the file (it chokes when >> blank lines or comments precede EXPORT). >> >> Werner supplied the patch below to fix libtool. The upstream bug >> appears to have a rather different set of patches. Either way, the >> problem should be cleaned up in libtool, as it's causing a series of >> workarounds for cross-building things on debian for the Windows >> platform. >> >> Is there some reason for the delay upstream besides lack of time to work >> on it? Should debian go ahead and apply one of the proposed patches >> downstream in the meantime? > > From the patch itself: > > There is no need to send this upstream. Upstream's git master has a > lot of changes including a similar fix for this problems. There are > no signs that a libtool 2.4.3 will be released to fix this problem and > thus we need to stick to our copy of 2.4.2 along with this patch. > > It is quite some time libtool 2.4.3 was released, the latest release is 2.4.6 > now. Can you check that update helps?
Hi! The libtool patch from https://debbugs.gnu.org/13414 is better than the debian patch from https://bugs.debian.org/814951 in every aspect that I can see and should indeed help. For reference, the libtool patch was committed here http://git.savannah.gnu.org/cgit/libtool.git/commit/?id=a5a4944fbb2bbd (three years old, released one year ago in 2.4.3) Cheers, Peter