[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: MinGW/Cygwin wrapper bug
From: |
Ralf Wildenhues |
Subject: |
Re: MinGW/Cygwin wrapper bug |
Date: |
Tue, 4 Dec 2007 22:33:10 +0100 |
User-agent: |
Mutt/1.5.13 (2006-08-11) |
* Bob Friesenhahn wrote on Tue, Dec 04, 2007 at 10:30:25PM CET:
> >Which of the two suspected setups is the failing one?
>
> To make things more clear, the problem is entirely which DLL is used
> when the wrapper script/program is executed. Libtool builds a correct
> DLL, but when 'make check' is executed and the installation 'bin'
> directory is in the executable search path (PATH) then a similar DLL
> from the installation 'bin' directory is used rather than the one that
> libtool just built. Unless DLL interfaces have been removed since the
> previous install, the user is not likely to immediately (if ever)
> notice that the wrong DLL is used for testing. This sort of bug
> causes much frustration on the part of developers.
OK, thanks, I guess I know now what the failure is.
> Since DLLs are installed in the installation 'bin' directory, it is
> common/normal for PATH to also include the installed DLL.
>
> In order to avoid this problem, PATH must be populated to include any
> necessary .libs directories prior to the already existing PATH. PATH
> is as close as it comes to LD_LIBRARY_PATH under Windows.
Sure.
But I won't write a fix before I get the answer to the question whether
the test I just wrote exposes the bug. Answer that please. And include
the Libtool version you have used. Thanks.
Cheers,
Ralf