X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=0.4 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_YG
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
In-Reply-To:	<4EE7987B.8030208@cs.utoronto.ca>
References:	<CAGVbXL7YGp-WsEx4QooOCX_44GB2gx_C5hNBKkGbXXT_y3zTEg AT mail DOT gmail DOT com> <4EE7987B DOT 8030208 AT cs DOT utoronto DOT ca>
Date:	Tue, 13 Dec 2011 10:45:08 -0800
Message-ID:	<CAGVbXL6772ds2XcDyJuz9PB76h4Crv_S1RmgF3RATcqcvTm_zA@mail.gmail.com>
Subject:	Re: cyg*.dll, linking
From:	Brian Craft <bcboy AT thecraftstudio DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On Tue, Dec 13, 2011 at 10:24 AM, Ryan Johnson wrote:
> On 13/12/2011 1:16 PM, Brian Craft wrote:
>>
>> I'm building a few libraries which are dependencies of a program I'm
>> building. Most of them build via autotools. Doing "make install"
>> installs files *.a, *.la, *.dll.a. Linking the executable succeeds
>> without error, however when running it, the loader complains that it
>> can't find cyg*.dll files. E.g. if it was libfoo.a that was installed,
>> the executable wants cygfoo-6.dll to run.
>>
>> These cyg-*.dll files exist in the build directories, generally in
>> src/.libs . The program will run if I add all of these to the PATH.
>>
>> Seems like either the link or the install isn't working as it should.
>> Are there docs anywhere that explain how this is supposed to work?
>
> The lib*.a file is a stub which allows proper linking of the actual dll
> (exporting symbols, etc.). Linking against it doesn't remove the need to
> have the cyg*.dll available at runtime.
>

Ok, but why don't autotools know about this? And why don't I see
cyg*.dll files, for example, in /usr/lib?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -