X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 	tests=AWL,BAYES_00,J_CHICKENPOX_62,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <4A7F47D8.9060409@gmail.com>
Date: Sun, 09 Aug 2009 23:04:08 +0100
From: Dave Korn <dave DOT korn DOT cygwin AT googlemail DOT com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: libffi-3.0
References: <6910a60907272310q54f29289l454117aff82afd5a AT mail DOT gmail DOT com> <4A6ED94B DOT 8020003 AT gmail DOT com> <4A7E725C DOT 8010706 AT users DOT sourceforge DOT net> <4A7ED3C9 DOT 70700 AT cwilson DOT fastmail DOT fm> <4A7F098B DOT 6030904 AT users DOT sourceforge DOT net> <4A7F1317 DOT 4050800 AT gmail DOT com> <4A7F4184 DOT 6090704 AT users DOT sourceforge DOT net>
In-Reply-To: <4A7F4184.6090704@users.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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

Yaakov (Cygwin/X) wrote:

> From a quick scan of the gcc patches list, it looks like they just
> synced the code between gcc and libffi.  But, AFAICS from gcc SVN, they
> didn't add a libffi.pc pkg-config file, which the standalone version
> provides and some libffi-dependent packages expect to find.  (Yes, I
> know how to override a pkg-config check, but still...)

  Ah, I didn't think of pkg-config.  Hmmmm....  now I have to go away and ponder
for a bit.

> That would be nice, but that won't be available until gcc-4.5, right?
> Until then, is the libffi in gcc-4.[34] work well enough on x86 to use
> in the meantime, particularly if the package explicitly depends on
> libffi-3.0?

  The current one isn't perfect, no, but is probably marginally better than
anything built from the pre-merge upstream libffi repository.  Even after the
merge there were still a bunch of bugs, but I've fixed them in GCC and am just
waiting for one of the guys with privs to sourceware to check them in for me.

  I've backported the fixed libffi for the 4.3 series, so if I get another
release done from there it'll have a good libffi in it.  So, whatever happens
next, we'll get a good libffi out of it.

    cheers,
      DaveK

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple