Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
To: "Marcus G. Daniels" <mgd@santafe.edu>
Cc: cygwin@cygwin.com, java@gcc.gnu.org
Subject: Re: gcc 3.3.1-3, loading .la files from gcj-compiled apps
References: <3FA5590F.6060308@santafe.edu>
From: Tom Tromey <tromey@redhat.com>
Reply-To: tromey@redhat.com
X-Attribution:  Tom
X-Zippy:  The appreciation of the average visual graphisticator alone is worth
 the whole suaveness and decadence which abounds!!
Date: 07 Nov 2003 13:31:52 -0700
In-Reply-To: <3FA5590F.6060308@santafe.edu>
Message-ID: <87oevnly2v.fsf@fleche.redhat.com>
Lines: 25
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

>>>>> "Marcus" == Marcus G Daniels <mgd@santafe.edu> writes:

Marcus> Would it be possible to add a -D_WIN32 to the libjava/libltdl
Marcus> Makefile for Cygwin?

It looks like it would be a bit more in line with existing code to
just add it to libltdl/ltdl.h.

Could you look at how the upstream libltdl handles it?  We
occasionally talk about importing a new version, I wonder if that
would fix this for you.

Marcus> Also, I found I had to duplicate the stack copy of `buf' in
Marcus> java::lang::Runtime:_load in order to avoid it getting wiped
Marcus> out from the the exception getting caught.

Could you be more explicit about this?  Catching an exception
shouldn't trash this array... if it does, doesn't that mean there is a
bug somewhere else?

The ltdl.c patch looks ok-ish, provided (as you noted) it is cleaned
up to be cygwin specific.  Again, ideally we'd do this via the
upstream libltdl.

Tom

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

