bug-libtool
[Top][All Lists]
Advanced

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

Re: Cygwin, wrong DLLs used for tests


From: Bob Friesenhahn
Subject: Re: Cygwin, wrong DLLs used for tests
Date: Tue, 12 Jan 2010 14:57:50 -0600 (CST)
User-agent: Alpine 2.01 (GSO 1266 2009-07-14)

On Tue, 12 Jan 2010, Ralf Wildenhues wrote:

* Bob Friesenhahn wrote on Tue, Jan 12, 2010 at 04:55:42AM CET:
In case it has been forgotten,

Hmm.  I don't remember a prior bug report to this end.

It was mentioned at least four years ago, before there was even a C wrapper for Cygwin.

with libtool 2.2.6b (and libtool
HEAD), and for software built under Cygwin, 'make check' does not
use the DLLs just built in the tree.  Even after installation and
with the installation bin directory first in the executable search
PATH, 'make check' does not use the new DLLs.  Instead, 'make check'
uses similar DLLs from Cygwin's /lib directory.  Even Cygwin's
altered libtool behaves similarly.

Is this about tests in the Libtool package itself, or about packages
using libtool?

Possibly both.

I am not sure how to solve the problem since it may be an artifact
of Windows behavior.

Well, usually, uninstalled programs get shell or C wrappers which modify
$PATH to point to uninstalled libraries.

Yes. It could be the C wrapper, or it could be if Windows looks in the directory containing the Cygwin DLL first.

Bob
--
Bob Friesenhahn
address@hidden, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/




reply via email to

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