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 14:12:45 -0400	[thread overview]
Message-ID: <59b990d09a2283bc157c966575cbbfed@asuka> (raw)
In-Reply-To: <200509021307.23166.vapier@gentoo.org>

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

On 2005-09-02 13:07:23 -0400 Mike Frysinger <vapier@gentoo.org> wrote:
>> 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.)
> 
> so has this all been integrated into the gcc ebuilds or does it need 
> to be or 
> ... ?
> -mike

> =gcc-3.4.3-r1 and <gcc-4* compiles and installs libffi seperately if 
> 'objc' is used (regardless of 'gcj', which always installs it); i.e. 
> the patch is already in there for that stated range of versions.

For gcc-4*, from what I looked at, the patch will also be quite easy
to make.  I've talked to one of the gcc/objc maintainers, and 4.1.0
might already offer libffi as a sepate build target (i.e. no need for
a patch to make it one).

For gcc-3.3, I looked at it way back when, and gave up ... so it might
not be difficult, I suppose, just significantly different enough from
the patch that works with gcc-3.4.

The dev-libs/libffi ebuilds are based on early libstdc++-v3 ebuilds
... but unlike libstdc++-v3, there's really no reason to offer it as a
seperate package, especially since gcc offers it.

The most ideal scenario is, across all gcc versions, 'objc' only
installs objc support, 'gcj' keeps doing it's gcj thing, and a new
flag 'libffi' installs libffi regardless of 'objc' or 'gcj'.  As one
of the few foreign function interface libraries out there (ffcall
comes to mind as well), libffi may be useful to some outside of
objc+GNUstep or gcj.

__armando

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

iD8DBQFDGJYcwgiTPLI9xhcRAs28AKCG8i2jrko1UgDMWPgJUq/CCTFPHACgipZC
pGgqI67R3u8O8HgI6O62sJY=
=46E2
-----END PGP SIGNATURE-----

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2005-09-02 18:16 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
2005-09-02 17:07       ` Mike Frysinger
2005-09-02 18:12         ` Armando Di Cianno [this message]
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=59b990d09a2283bc157c966575cbbfed@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