delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2004/10/13/15:26:29

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
In-Reply-To: <1351779159125.20041013175737@familiehaase.de>
References: <3262F821-1588-11D9-B5B2-000A9599D97C AT mac DOT com> <41607B7D DOT 1060104 AT mail DOT mcgill DOT ca> <8AD73160-18B2-11D9-8E10-000A95A76622 AT mac DOT com> <1097219897 DOT 17347 DOT 106 DOT camel AT localhost DOT localdomain> <591336448812 DOT 20041008145906 AT familiehaase DOT de> <CF1AEB5C-192F-11D9-9065-000A95A76622 AT mac DOT com> <1351779159125 DOT 20041013175737 AT familiehaase DOT de>
Mime-Version: 1.0 (Apple Message framework v619)
Message-Id: <AF57314C-1D4D-11D9-BFD0-000A9599D97C@mac.com>
Cc: "Grzegorz B. Prokopski" <gadek AT debian DOT org>, cygwin AT cygwin DOT com,
Peter Lovell <vpndev AT mac DOT com>
From: Peter Lovell <vpndev AT mac DOT com>
Subject: Re: SableVM & Cygwin (was: Re: sablevm + windows)
Date: Wed, 13 Oct 2004 15:25:47 -0400
To: SableVM Developers Mailing List <sablevm-devel AT sablevm DOT org>,
"Gerrit P. Haase" <freeweb AT nyckelpiga DOT de>

Hi Gerrit,
many thanks for this. Great !

Speaking only for myself, I believe that option (2) would be the 
appropriate one. It might be nice to include it also back to gcc but I 
suspect that sablevm developers might prefer to not have that 
dependency.

I'll fetch your patches and test and let you know.

Many thanks.....Peter

On Oct 13, 2004, at 11:57 AM, Gerrit P. Haase wrote:

> Hi Peter,
>
> coming back to this now.
>
>> I'm also willing to help port and maintain.
>
> Fine.  I have to offer two possible scenarios.
>
> 1.
> I have a stripped down standalone libffi package with a shared libffi
> now.  This version is based on the sources from the cygwin release of
> gcc-3.3.3. You can take this package and maintain it, that means update
> it when Cygwin GCC is updated and integrate the changes happened in the
> libffi subdirectory.
>
> 2.
> Include this stripped down libffi version with the SableVM sourcetree
> and link libffi into the main DLL as a convenience library.
>
> IMO it would be easier to keep it uptodate when it is included with the
> SableVM sources and also distributed this way.  So one can continue 
> when
> you or me are gone.
>
> I have a patch I can send you, there is the stripped down libffi
> integrated in the SablVM build.  The standalone libffi is available as
> separate package from my webserver:
> http://anfaenger.de/cygwin/cygwin-1.5/libffi-cygwin-standalone/
>
> Ready compiled SableVM binary and source package:
> http://anfaenger.de/cygwin/cygwin-1.5/saqblevm/
>
> The source package includes also the patch and uses a statically 
> libffi,
> so it doesn't need a FFI DLL.  Could you verify that this SableVM works
> as expected, please?
>
> Classpath is still compiling.
>
>
> Gerrit
> -- 
> =^..^=                                     
> http://nyckelpiga.de/donate.html
>
>
> _______________________________________________
> SableVM-devel mailing list
> SableVM-devel AT sablevm DOT org
> http://sablevm.org/lists/control/listinfo/sablevm-devel
>


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


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019