Marco Atzeri wrote:
> I found also a further problem.
> In one case (hdf5) I found no way to build shared libs
> as the libtool always had "build_libtool_libs=no"
>
> as "extrema ratio" I added a
> sed -e "1,100s/^build_libtool_libs=no/build_libtool_libs=yes/" -i libtool
>
> between cygconf and cygmake, and the build completed fine.
>
> Reverting to libtool-2.2.6 solved this issue.
I noticed that the output from 'file' has changed recently, e.g.:
/bin $ file -L /bin/ls.exe
/bin/ls.exe: MS-DOS executable PE for MS Windows (console) Intel 80386 32-bit
Maybe this will help? Or perhaps something similar elsewhere. Libtool uses
file in several ways to help it decide what it's going to build.
/bin $ diff -pu libtool.orig libtool
--- libtool.orig 2009-03-15 23:19:29.500000000 +0000
+++ libtool 2009-03-15 23:21:14.906250000 +0000
@@ -3273,6 +3273,7 @@ func_win32_libid ()
*executable*) # but shell scripts are "executable" too...
case $win32_fileres in
*MS\ Windows\ PE\ Intel*)
+ *PE*\ *MS\ Windows\ *Intel*)
win32_libid_type="x86 DLL"
;;
esac
@_______. .
( /"\
||--||(___)
'" '"'---'
/bin $
cheers,
DaveK
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
