libtool-patches
[Top][All Lists]
Advanced

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

Re: [PATCH] [cygwin|mingw] fix dlpreopen with --disable-static take 2


From: Peter Rosin
Subject: Re: [PATCH] [cygwin|mingw] fix dlpreopen with --disable-static take 2
Date: Thu, 15 Jan 2009 13:32:08 +0100
User-agent: Thunderbird 2.0.0.19 (Windows/20081209)

Den 2009-01-13 16:41 skrev Charles Wilson:
Peter Rosin wrote:
Den 2009-01-06 02:06 skrev Charles Wilson:
Maybe under that name. But a libbfd-ified version of impgen (as a
replacement for the IMO totally broken -- but part of mingw-utils-0.3 --
reimp program), that happens to also supply an --identify <foo>
--identify-ms functionality? Not so far-fetched.
Right, but it still seems as if this new fixed impgen tool is closer
to MinGW than to MSYS proper. However, as you say, better ask on a better
list...

After playing with this idea for a while, it made more sense actually to
separate the impgen2 functionality from the dllname stuff. It's not yet
ready for prime time (and I'm trying to keep it in sync with on-going
changes to dlltool in binutils HEAD), but I'll send my latest version of
 these new tools to you offlist.  They compile with both cygwin-gcc
(using libiberty and libbfd from 20080624), and with mingw-gcc-3.4.5
(not sure what binutils version I have; one of the more recent releases
from mingw/sourceforge I'm sure).

Works for import libs built by MSVC 2005, didn't test any other version.

I'm only saying that from the "binutils p.o.v." it makes at least some
sence to report all imported dlls. At least optionally, but again, this
was just a minor point...

A new patch to binutils' dlltool was accepted that makes the following
changes to --identify:
  1) automatically determines -- and operates with -- MS-style or
binutils-style implibs

I thought that I did build three dependent libraries A->B->C using MSVC
and MinGW alternatingly  (MSVC for A and C, MinGW for B, or the other way
around) just for testing interoperability, but that was a long
time ago... And I'm not sure I really did it or if it worked. I guess
I should do it again (if I did it, otherwise I should just do it).

  2) by default, lists all imported DLLs
  3) new --identify-strict flag causes multiple imported DLLs to be
reported as an error
http://sourceware.org/ml/binutils/2009-01/msg00152.html

Cool.

I'm hoping for this to get into MSYS 1.0.11 (or 12...) so that we can
rely on its presence.

Cheers,
Peter





reply via email to

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