Re: OBJDUMP incorrect on cross-compiles to mingw32

[Simon Josefsson]

Ralf Wildenhues <address@hidden> writes:

> * Simon Josefsson wrote on Thu, Jun 22, 2006 at 12:28:04PM CEST:
>> Ralf Wildenhues <address@hidden> writes:
>> > * Simon Josefsson wrote on Wed, Jun 21, 2006 at 03:48:08PM CEST:
>> >
>> >> # Used on cygwin: object dumper.
>> >> OBJDUMP="objdump"
>> >> 
>> >> This is incorrect on my system, the "objdump" binary is the
>> >> i686-pc-linux-gnu objdump, which doesn't understand the Windows DLLs.
>> >> The "correct" objdump would be called i586-mingw32msvc-objdump.
>> >
>> > Do you use AC_LIBTOOL_WIN32_DLL?
>
>> No.  The document for that macro seems a bit terse, but I'm not using
>> __declspec(dllexport) etc, so I guess I shouldn't use the macro?
>
> Yes, the documentation is terse.  But I think you should use the macro.

Yup, I'm now doing this in my packages, and it works fine.

I think the conclusions is that the documentation is slightly
outdated, and should be updated to say that if you want to build
shared libraries under win32, you must use the macro.  Further, it may
be simpler if libtool were to call the AC_LIBTOOL_WIN32_DLL macro by
default.  The macro only set up paths to OBJDUMP/AS/DLLTOOL; commands
that libtool will invoke in any case (I wonder what would have
happened if I didn't happen to have a tool "objdump" on the system).

Thanks,
Simon