public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/46819] [4.6 Regression] libffi is always built
Date: Wed, 08 Dec 2010 10:17:00 -0000 [thread overview]
Message-ID: <bug-46819-4-86kZcb5q9E@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46819-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46819
--- Comment #2 from rguenther at suse dot de <rguenther at suse dot de> 2010-12-08 10:17:09 UTC ---
On Tue, 7 Dec 2010, ian at airs dot com wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46819
>
> Ian Lance Taylor <ian at airs dot com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |ian at airs dot com
>
> --- Comment #1 from Ian Lance Taylor <ian at airs dot com> 2010-12-07 19:00:26 UTC ---
> I just did a complete bootstrap with --enable-languages=c and libffi was not
> built. I did various configure runs with various options, and
> TARGET_CONFIGDIRS appeared to generally include libffi when appropriate and not
> include it when appropriate.
>
> What configure options are you using?
I am using
--enable-languages=c,c++,objc,fortran,obj-c++,java,ada --disable-libgcj
which formerly disabled building of libffi, but now leaves it enabled
(even if go is not enabled).
I didn't remember that, so maybe the issue isn't that important. But
maybe we can have a --disable-libffi configure option? (continuing
to disable libffi with --disable-libgcj if Go is not build would be
also ok of course).
Richard.
next prev parent reply other threads:[~2010-12-08 10:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 11:55 [Bug bootstrap/46819] New: " rguenth at gcc dot gnu.org
2010-12-06 11:55 ` [Bug bootstrap/46819] " rguenth at gcc dot gnu.org
2010-12-07 19:00 ` ian at airs dot com
2010-12-08 10:17 ` rguenther at suse dot de [this message]
2010-12-10 14:47 ` ian at gcc dot gnu.org
2010-12-10 15:26 ` ian at airs dot com
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=bug-46819-4-86kZcb5q9E@http.gcc.gnu.org/bugzilla/ \
--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).