From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15458 invoked from network); 21 Jul 2004 23:01:51 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 21 Jul 2004 23:01:51 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.34) id 1BnQ5u-0004CE-Bc for arch-gentoo-dev@lists.gentoo.org; Wed, 21 Jul 2004 23:01:50 +0000 Received: (qmail 22329 invoked by uid 89); 21 Jul 2004 23:01:39 +0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 534 invoked from network); 21 Jul 2004 23:01:38 +0000 From: Travis Tilley Reply-To: lv@gentoo.org Organization: Gentoo To: gentoo-dev@lists.gentoo.org Date: Wed, 21 Jul 2004 19:02:06 -0400 User-Agent: KMail/1.6.2 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="windows-1250" Content-Transfer-Encoding: quoted-printable Message-Id: <200407211902.06366.lv@gentoo.org> Subject: Re: [gentoo-dev] RFC: stitching GNUstep into portage (resend: corrupted for some) X-Archives-Salt: 9dc8e23e-d22e-4d14-9afc-583515048c91 X-Archives-Hash: caacadb883555ea25e38ef5c71d3639c On Wednesday 21 July 2004 05:15 pm, Armando Di Cianno wrote: > * ffcall v. libffi considerations > > Currently, gnustep-base requires the use of a foreign function interface.= =20 > In short, all this library needs to do is stack frame handling. > > Ffcall uses trampolines to do this, and it was quickly pointed out to me = by > the more security minded dev's that this is a Bad Thing. > > Sadly, libffi has it's considerations as well. Some years ago, it was > basically =93parked=94 inside of GCC. This makes the ebuilds I've writte= n for > libffi slightly annoying, in that all GCC sources have to be downloaded; > however, I can easily monitor changes to gcc ebuilds, and the libstdc++-v3 > ebuild, which I based my libffi ebuilds off of, to maintain the fixes for > specific architectures created in those ebuilds. > > Use of libffi has resulted in full to partial success using (my) GNUstep > ebuilds on ppc, sparc, and amd64 as well as x86. Sadly sparc and amd64 > need some actual GNUstep core library work, as some misuse of assumptions > about word sizes have begun to show themselves. i'd like for libffi to be the default if possible, since it's required for= =20 gnustep to work with hardened at all, or on archs like the one i happen to= =20 use. also, isnt ffcall unmainained? =2D-=20 Travis Tilley -- gentoo-dev@gentoo.org mailing list