[Top][All Lists]

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

Re: mingw win64 comatibility

From: Ralf Wildenhues
Subject: Re: mingw win64 comatibility
Date: Tue, 21 Oct 2008 05:10:35 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

Hello Alon,

Thanks for the report.

* Alon Bar-Lev wrote on Mon, Oct 20, 2008 at 03:19:50PM CEST:
> The func_win32_libid is not working correctly when win64 objects are found.
> The file format is "file format pe-x86-64".
> The attached patches for 1.5.26, 2.2.6a for the resulting libtool script.
> I did not know where to put this in libtool source, can you please
> look into it?

It needs to be done in libltdl/config/ltmain.m4sh.

> --- libtool.2.2.6a    2008-10-20 14:21:57.000000000 +0200
> +++ libtool   2008-10-20 14:21:42.000000000 +0200
> @@ -3073,7 +3073,7 @@ func_win32_libid ()
>      ;;
>    *ar\ archive*) # could be an import, or static
>      if eval $OBJDUMP -f $1 | $SED -e '10q' 2>/dev/null |
> -       $EGREP 'file format pe-i386(.*architecture: i386)?' >/dev/null ; then
> +       $EGREP 'file format pe-i386(.*architecture: i386)?|file format 
> pe-x86-64?' >/dev/null ; then

The trailing ? after pe-x86-64 is wrong, pleasse drop it.

>        win32_nmres=`eval $NM -f posix -A $1 |
>       $SED -n -e '
>           1,100{

Can you be bothered to check out the Libtool git tree or a nightly
snapshot (see homepage for links) and, with above change, build it
and run the testsuite on win64, please?  We'd be interested in any
failures of
  make -k check

(add VERBOSE=yes for verbose output of the old testsuite, and send
tests/testsuite.log for failure of the new one).

You'd need Autoconf for rebuilding Libtool, and also Automake for
running all tests.


reply via email to

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