public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Armando Di Cianno <fafhrd@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] gcc-3.3.6 for x86 stable
Date: Fri, 02 Sep 2005 13:00:46 -0400	[thread overview]
Message-ID: <e2160568ddbdc29ce41c11f83a362bc4@asuka> (raw)
In-Reply-To: <200509021205.38680.vapier@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2005-09-02 12:05:38 -0400 Mike Frysinger <vapier@gentoo.org> wrote:

> On Friday 02 September 2005 11:50 am, Gustavo Zacarias wrote:
>> Mike Frysinger wrote:
>>> any known/standing issues people wish to get out before we move 
>>> gcc-3.3.6
>>> to x86 stable ?
>> 
>> You'll also need a matching dev-libs/libffi, otherwise it'll go all
>> circular for people using GNUstep.
> 
> toolchain doesnt maintain libffi, the gnustep peeps do ...
> -mike

The gnustep herd (me) isn't going to be able to do much until the
weekend...hey, the weekend starts in about 4 hours for me ...

I've been trying to phase out dev-libs/libffi for a long while...if
someone can figure out a patch for gcc-3.3 series that compiles and
installs libffi w/o building the entirety of gjc/java/etc, that would
be fantastic; gcc-3.4 series has had this for a long time, and the
patch is incredibly simple -- my one attempt at doing this for gcc-3.3
series proved fruitless.  (The little bit of monkeying I've done with
gcc-4 series has proved easy wrt to this.)

'objc' USE flag pushes the patch on, so one can have USE="-gcj +objc"
... if I, or someone else who knows GCC innards better than I, figures
out the patch for gcc-3.3, I'd suggest adding a 'libffi' USE flag (so
the 'objc' flag goes back to just enabling ObjC), so the few misc.
ebuilds that use it besides GNUstep (sablevm comes to mind), can
enable libffi to be built (w/o gcj or even objc).

__armando di cianno
aka fafhrd

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1-ecc0.1.6 (GNU/Linux)
Comment: Using the GPG bundle for GNUMail

iD8DBQFDGIU8wgiTPLI9xhcRAtowAJ0RwEgBLOAF+f+rSKR3RUVs+ezDPQCgiPiA
dTULkSYe0hXN8UNUD+KoV1U=
=lQaw
-----END PGP SIGNATURE-----

-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2005-09-02 17:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-02  5:07 [gentoo-dev] gcc-3.3.6 for x86 stable Mike Frysinger
2005-09-02 12:40 ` Mike Doty
2005-09-02 12:48   ` Mike Frysinger
2005-09-02 15:50 ` Gustavo Zacarias
2005-09-02 16:05   ` Mike Frysinger
2005-09-02 16:24     ` Ciaran McCreesh
2005-09-02 17:00     ` Armando Di Cianno [this message]
2005-09-02 17:07       ` Mike Frysinger
2005-09-02 18:12         ` Armando Di Cianno
2005-09-02 19:46           ` Mike Frysinger
2005-09-02 20:36             ` Armando Di Cianno

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e2160568ddbdc29ce41c11f83a362bc4@asuka \
    --to=fafhrd@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox