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] RFC: stitching GNUstep into portage (resend: corrupted for some)
Date: Thu, 22 Jul 2004 09:26:30 -0400	[thread overview]
Message-ID: <ef7c88aca8c579a075a7cb8978f92d35@mudra> (raw)
In-Reply-To: <200407211902.06366.lv@gentoo.org>

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

On 2004-07-21 19:02:06 -0400 Travis Tilley <lv@gentoo.org> wrote:
> i'd like for libffi to be the default if possible, since it's 
> required for 
> gnustep to work with hardened at all, or on archs like the one i 
> happen to 
> use. also, isnt ffcall unmainained?

There's a good chance that ffcall is, for all intents and purposes,
unmaintained, although people do still regularly use it.  Libffi is a
little less "popular", but for our ends, it is really the only choice.
   Sadly, the gcc build process doesn't compile it unless java and c++
are enabled, but if the target is only "install-target-libffi", it
only increased the build time from 1 minute to 7, and not to ~35
minutes for the entire gcc w/ java.

Does anyone know if the different arch testing machines available can
host remote X sessions?  If so, I really should get in touch with the
maintainer of the amd64 machine, and get to the root of the issues
with the GNUstep core library and amd64.  So far, gdb backtraces on
that arch have died in the same function, so I'm crossing my fingers
it remains only that one.

__Armando Di Cianno
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using the GPG bundle for GNUMail.app

iD8DBQFA/8CFwgiTPLI9xhcRAjxFAJ9q3l3KinQMuqEHFw+RrAxg/z3Q6QCfdY2L
8GaUVIi+GqjxKbDSmMCjes4=
=yCbM
-----END PGP SIGNATURE-----


--
gentoo-dev@gentoo.org mailing list


      reply	other threads:[~2004-07-22 13:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-21 21:15 [gentoo-dev] RFC: stitching GNUstep into portage (resend: corrupted for some) Armando Di Cianno
2004-07-21 23:02 ` Travis Tilley
2004-07-22 13:26   ` Armando Di Cianno [this message]

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=ef7c88aca8c579a075a7cb8978f92d35@mudra \
    --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