public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egall at gwmail dot gwu.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: Tue, 28 Apr 2015 15:26:00 -0000 [thread overview]
Message-ID: <bug-11660-4-fKTg0DBZpu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-11660-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=11660
Eric Gallager <egall at gwmail dot gwu.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egall at gwmail dot gwu.edu
--- Comment #11 from Eric Gallager <egall at gwmail dot gwu.edu> ---
Doesn't libffi also get built if go is selected as a language? I can't verify
it for myself due to bug 46986, but based on my reading of Makefile.def, it
seems like building libgo should cause libffi to be built, as well...
next parent reply other threads:[~2015-04-28 15:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11660-4@http.gcc.gnu.org/bugzilla/>
2015-04-28 15:26 ` egall at gwmail dot gwu.edu [this message]
[not found] <bug-11660-3827@http.gcc.gnu.org/bugzilla/>
2005-10-23 0:08 ` pinskia at gcc dot gnu dot org
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
2004-12-12 4:32 ` pinskia at gcc dot gnu dot org
2005-04-21 16:42 ` pinskia at gcc dot gnu dot org
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-11660-4-fKTg0DBZpu@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).