Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <20000328183749.18623.qmail@web209.mail.yahoo.com> Date: Tue, 28 Mar 2000 10:37:49 -0800 (PST) From: Craig Stevenson Reply-To: craig DOT stevenson AT ieee DOT org Subject: dll dependencies To: cygwin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Hi: I have some test code I am trying to get to work on cygwin. There are two toy dlls, called A and B, and A uses B. B does not use anything special. In the app main uses dlopen() and dlsym() on B without any problems. The same procedure on A generates a problem in that it needs B and cannot seem to load it. If I manually load B before A it will execute correctly with a Warning about failing to load A on stderr. If I don't load it first it will fail out totally with a Win32 error about inability to load a dll. Figuring windows dll's are stupid, I put a dlopen call to B in A's _dll_init() function. But this did not work either. I am using the straight 20.1 version cygwin. I have the latest snapshot and am attempting to compile *-src-* (which just failed). Sigh... Is this known behavior?? What is the straightforward way to deal with dll dependencies in the context of manually calling dlopen()?? Thanks. ===== -- Craig Stevenson -- Home Page: http://www.sdc.org/~craigs/ -- Recently computed: The 200 billionth digit of pi is 2. __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com