This is the mail archive of the
mailing list for the Cygwin project.
Re: Questions about missing DLLs and program behvior, and symlinks to DLLs (also, a small setup recommendation)
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 12 Jan 2009 11:18:48 -0500
- Subject: Re: Questions about missing DLLs and program behvior, and symlinks to DLLs (also, a small setup recommendation)
- References: <496AC6E9.email@example.com>
- Reply-to: cygwin at cygwin dot com
On Sun, Jan 11, 2009 at 08:28:25PM -0800, firstname.lastname@example.org wrote:
>Hello! I haven't been able to find anything about this in the archives.
>I recently decided to replace my old Cygwin installation with a new,
>fresh one, so everything should be up-to-date here. [That's my
>recommendation: perhaps a way to make it easier to install fresh; it was
>necessary to rename both the old Cywin installation and the location of
>the downloaded installation packages to keep setup from finding them.]
>The DLL questions are regarding programs compiled within Cygwin: when a
>program can't find a DLL, one expects some sort of error message to that
>effect, and which would indicate the DLL in question. As my demo below
>shows, programs simply exit silently and unceremoniously when that happens.
That is fixed in Cygwin 1.7.x.
>Second, symlinking to DLLs doesn't enable programs to find them, as is
>also shown below.
Right. Symlinks are a Cygwin invention. Cygwin doesn't start running
until after DLLs are loaded. So, since Windows does not know about Cygwin
symlinks there is no way that they can be used to symlink DLLs.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html