Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-ID: <3B9B7E97.3020606@ece.gatech.edu> Date: Sun, 09 Sep 2001 10:37:11 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010713 X-Accept-Language: en-us MIME-Version: 1.0 To: Dmitry Timoshkov CC: cygwin@cygwin.com Subject: Re: binutils auto-import bug References: <3B9B0C1F.7090504@ece.gatech.edu> <3B9B0D6E.8050104@ece.gatech.edu> <014901c13931$581ab2d0$c3823bd5@dmitry> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Dmitry Timoshkov wrote: > "Charles Wilson" wrote: > > >>>The reason for the quotation marks is: Paul's patch doesn't actually fix >>>the bug. It just detects the condition that *causes* the bug, prints a >>>diagnostic message, and exits with error. >>> >>Oh, one other thing: this is *meant* as an interim step towards actually >>*fixing* the bug. But, because of certain idiosyncracies of the windows >>dynamic loader, detection-and-prevention, as in the current patch, MAY >>be the best we can do. >> >>It isn't yet clear. >> > > Did you try to use different compiler/linker? For instance from MIcrosoft > or Borland? How do they behave in your tests? Ummm...you're missing the point. This is about how the binutils linker links, when the "auto-import" feature is used. NOT about how any other linker would work in some hypothetical situation. As far as the DLLs themselves are concerned, if they are produced by binutils-ld, it is theoretically possible to create a .lib-style import library for the DLL, and then use MS-link.exe to link to them, if the client code uses __declspec(dllimport). MS nor Borland linkers HAVE an "auto-import" feature. So how could I test it? --Chuck Auto -- 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/