Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-ID: <20050530085023.73565.qmail@web31714.mail.mud.yahoo.com> Date: Mon, 30 May 2005 01:50:23 -0700 (PDT) From: Sunil Subject: Re: dlopen doesn't use LD_LIBRARY_PATH ( was dlopen and cygcheck inconsistency) To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes I am not sure why the last email didn't reach the list, but here goes again. this issue is still un-resolved. Contrary to what cgf says, dlopen doesn't care about LD_LIBRARY_PATH while opening dependent DLLs of its argument. It opens the DLL if the depedent DLLs are found in the $PATH. I think cgf meant if I do dlopen("c.dll",..) it will try to find it in LD_LIBRARY_PATH (plus /usr/lib from 1.5.17). what happens in this case: dlopen("/a/b/c.dll",...) and c.dll depends on /a/b/d.dll. This dlopen of c.dll fails if /a/b is not in PATH, although it is in LD_LIBRARY_PATH. I don't think this is linux behaviour. Thanks, -Sunil __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/