X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=AWL,BAYES_00,SPF_NEUTRAL,TW_YG X-Spam-Check-By: sourceware.org Message-ID: <4EE7987B.8030208@cs.utoronto.ca> Date: Tue, 13 Dec 2011 13:24:59 -0500 From: Ryan Johnson User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: cyg*.dll, linking References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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 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. Ryan -- 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