Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <01ce01c2d608$fd8a0ac0$78d96f83@pomello> From: "Max Bowsher" To: "Charles Wilson" , "Ralf Habacker" Cc: "cygwin" References: <001201c2d5c2$68cd4550$755f07d5@BRAMSCHE> <3E500500.2080905@ece.gatech.edu> Subject: Re: [avail for test] libtool-devel-20030121-1 Date: Sun, 16 Feb 2003 22:16:01 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Charles Wilson wrote: >> Ralf Habacker wrote: >>>>> BTW: Do you know which libraries are also hybrid execpt of >>>>> cygwin1.dll ? >>> >>> >>>> There are about a half-dozen in /usr/lib/w32api -- and worse, the >>>> static >>> >>> members are "bad" variable types; if you make the static members >>> part of the DLL, then these vars can't be auto-imported without >>> using pseudo-relocs. Of course, since the DLLs are provided by MS, >>> we can't really modify what is in them. >>> >>> Thats very bad. >>> >> >> Yeah. I don't know why these implibs need to declare these static >> structures; it's possible that w32api is just following the lead of >> the corresponding .lib files in the MSVC distribution. >> >> But, that's neither here nor there. IF these crossbreed implibs are ^^^^^^^^^^^^^^^^^^ libuuid.a at least is static *only* - not crossbreed. So there really is no way for libtool know to allow it except by name. >> detected as "import libraries" then libtool will let you link a >> sharedlib using them as dependencies. Max. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/