Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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:	4U/6xbCR6FijIa8cO4A9Fg 1068253779
Message-ID:	<3FAC42D9.9040209@cwilson.fastmail.fm>
Date:	Fri, 07 Nov 2003 20:11:53 -0500
From:	Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
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:	"Marcus G. Daniels" <mgd AT santafe DOT edu>
Cc:	cygwin AT cygwin DOT com, 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>
In-Reply-To:	<3FAC1145.40706@santafe.edu>
X-Enigmail-Version:	0.76.1.0
X-Enigmail-Supports:	pgp-inline, pgp-mime

Marcus G. Daniels wrote:

>>
> As of yesterday, I believe Charles Wilson has convinced the libtool 
> maintainers to install the needed patches.  It uses dlopen if it can, 
> and then falls back to LoadLibrary if that fails.
> 

Actually, that change is all Gary V. Vaughan.

Here's the story: contrary to my post in this thread from two days ago, 
current cygwin libltdl DOES use dlopen exclusively.  What confused me 
was that there is some compatibility code in the LoadLibrary section, 
which in the distant past was used by libltdl on cygwin.

(Thus, if gcj/your-package uses an older libtool/older libltdl, it is 
possible you created your loadable modules in old, LoadLibrary mode. 
But for the last year or so, and in official libtool-1.5, cygwin libtool 
has been dlopen-only.)

I submitted a patch which removed all of the (dead) LoadLibrary/cygwin 
compatibility stuff.  Because it was not used at all, in current 
libtool/libltdl.

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.

--
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/

- Raw text -