public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/46819] New: [4.6 Regression] libffi is always built
Date: Mon, 06 Dec 2010 11:55:00 -0000	[thread overview]
Message-ID: <bug-46819-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46819

           Summary: [4.6 Regression] libffi is always built
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Keywords: build
          Severity: normal
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: rguenth@gcc.gnu.org
                CC: iant@google.com


Since introduction of Go we always build libffi and there is no way to disable
that.

libffi should only be built if either Java or Go is enabled.

Related workaround:

2010-12-03  Hans-Peter Nilsson  <hp@axis.com>

        PR libffi/46792
        * configure.ac (cris-*-elf, crisv32-*-elf): Disable target-libffi.
        * configure: Regenerate.


Ian, please restore previous behavior.  Thanks.


             reply	other threads:[~2010-12-06 11:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-06 11:55 rguenth at gcc dot gnu.org [this message]
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
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@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).