public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aperez at student dot santarosa dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/11660] libffi only builds when java is selected as language
Date: Fri, 02 Jul 2004 23:00:00 -0000 [thread overview]
Message-ID: <20040702230005.30534.qmail@sourceware.org> (raw)
In-Reply-To: <20030724122445.11660.dleeuw@made-it.com>
------- Additional Comments From aperez at student dot santarosa dot edu 2004-07-02 23:00 -------
I would also like to throw my support behind this modification/enhancement. This
is important/necessary for more than just java. GNUstep can use either libffi or
ffcall, and libffi is preferable for a number of reasons, but as of now it's a
massive pain in the ass to build because you have to check out way more than you
actually need. So the entire GNUstep community would benefit from this
modificaitons, as well as numerous other communities, including the pyobjc
community. I would prefer an --enable-libffi configure option as Andrew Pinski
suggests.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11660
next prev parent reply other threads:[~2004-07-02 23:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-24 12:24 [Bug target/11660] New: " dleeuw at made-it dot com
2003-07-24 12:41 ` [Bug bootstrap/11660] " pinskia at physics dot uc dot edu
2003-07-24 12:48 ` dennis at pruts dot nl
2003-07-24 12:57 ` pinskia at physics dot uc dot edu
2003-07-24 13:00 ` dennis at pruts dot nl
2003-07-24 15:33 ` ro at techfak dot uni-bielefeld dot de
2003-08-23 0:58 ` dhazeghi at yahoo dot com
2004-02-27 15:41 ` pinskia at gcc dot gnu dot org
2004-07-02 23:00 ` aperez at student dot santarosa dot edu [this message]
2004-12-12 4:32 ` pinskia at gcc dot gnu dot org
2005-04-21 16:42 ` pinskia at gcc dot gnu dot org
[not found] <bug-11660-3827@http.gcc.gnu.org/bugzilla/>
2005-10-23 0:08 ` pinskia at gcc dot gnu dot org
[not found] <bug-11660-4@http.gcc.gnu.org/bugzilla/>
2015-04-28 15:26 ` egall at gwmail dot gwu.edu
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=20040702230005.30534.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).