[Top][All Lists]

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

Re: RFA: libtool.m4

From: JonY
Subject: Re: RFA: libtool.m4
Date: Wed, 29 Apr 2009 18:53:54 +0800
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20080213 Thunderbird/ Mnenhy/

On 4/29/2009 15:26, Kai Tietz wrote:
2009/4/28 Ralf Wildenhues<address@hidden>:
[ adding bug-libtool; you can remove gcc-patches from followups ]

* Kai Tietz wrote on Tue, Apr 28, 2009 at 02:29:12PM CEST:
In the libtool.m4 in function _LT_CHECK_MAGIC_METHOD the current check
for mingw doesn't treat the x64 proper.
It checks for 'file_magic file format pei*-i386(.*architecture:
i386)?', what is right for 32-bit mingw, but for 64-bit version this
string needs to be changed to something like 'file_magic file format
pei*(.*architecture: i386)?'

I did the libtool testsuite run for w64 target and found no serious
issues (as I expected). But the underlying issue isn't tested in the
suite at all my initial post is pointing on. The problem is that the
pattern used (and so also in libtool itself) for detection if a dll
(windows shared object) is generated is wrong.

So, can you devise a short example, or ideally even a testsuite addition
to git Libtool that exposes this issue?  Alternatively, describe the
situation in which you encountered it.

in aclocal.m4 there is the line
'lt_cv_deplibs_check_method='file_magic file format
pei*-i386(.*architecture: i386)?'
which doesn't fit for 64-bit dlls.
lt_cv_deplibs_check_method='file_magic file format
pei*-(i386|x86_64)(.*architecture: i386)?'

If you are interest in the testrun files, please tell me. I can sent
them to you.

If there are no testsuite failures, then no, I don't need them.  Thanks.


Hello Ralf,

we found another issue about the pattern used for pe-i386 and the file
patterns for x86_64. JonY from the mingw-w64 team will continue this
thread and he will take care .
about it.


Hello all,

I am confused on the following 2 functions work.


Sorry my shell scripting was never good to begin with. So here are some possibly helpful info.

Running objdump -f on a system dll import lib gives:

dozs00000.o:     file format pe-x86-64
architecture: i386:x86-64, flags 0x00000039:
start address 0x0000000000000000

For 64bit dlls, objdump -f gives:

libltdl-7.dll:     file format pei-x86-64
architecture: i386:x86-64, flags 0x0000013b:
start address 0x000000006d4813d0

reply via email to

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