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 X-Sasl-enc: 2yWmaItynlppY7o6JJcW7g 1068255050 Message-ID: <3FAC47D6.5000907@cwilson.fastmail.fm> Date: Fri, 07 Nov 2003 20:33:10 -0500 From: Charles Wilson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030630 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cygwin AT cygwin DOT com Cc: java AT gcc DOT gnu DOT org Subject: Re: gcc 3.3.1-3, loading .la files from gcj-compiled apps References: <3FA5590F DOT 6060308 AT santafe DOT edu> <87oevnly2v DOT fsf AT fleche DOT redhat DOT com> <3FAC1145 DOT 40706 AT santafe DOT edu> <3FAC42D9 DOT 9040209 AT cwilson DOT fastmail DOT fm> <1068254431 DOT 1188 DOT 21 DOT camel AT localhost> In-Reply-To: <1068254431.1188.21.camel@localhost> X-Enigmail-Version: 0.76.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Robert Collins wrote: > On Sat, 2003-11-08 at 12:11, Charles Wilson wrote: > >>GVV went one better, and re-activated the LoadLibrary stuff, with cygwin >>compatibility code, as a FALLBACK option if-and-only-if dlopen on cygwin >>fails. THAT is what got committed to libtool CVS HEAD, and it's Gary's >>contribution, not mine. >> >>Now, whether this fixes your problem or just makes it worse, I don't know. > > > I suspect it'll make it worse, as it may well interfere with fork(). Hmm. I wonder if "The Right Thing To Do" is to ensure that libjava's version of ltdl.c is uptodate -- that is, taken from libtool-1.5 and not 1.4.x, and then rebuild libjava, the modules, etc. Or rebuild libjava so that it uses the system-installed version of cygltdl-3.dll and not a self-compiled one. Then, we'll at LEAST know that everything is speaking the same dlopen language. Plus, can somebody do an strace on the program that fails to load the .la files? And make sure that dlopen & friends ARE in fact being called, as they should be on the cygwin platform? (That is, instead of asking for LoadLibrary workarounds, let's make sure that we're actually using -- and that the modules themselves are expecting -- the cygwin-provided, fork()-friendly dlopen stuff). -- Chuck -- 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/