public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dleeuw at made-it dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/11660] New: libffi only builds when java is selected as language Date: Thu, 24 Jul 2003 12:24:00 -0000 [thread overview] Message-ID: <20030724122445.11660.dleeuw@made-it.com> (raw) PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11660 Summary: libffi only builds when java is selected as language Product: gcc Version: 3.3 Status: UNCONFIRMED Severity: minor Priority: P2 Component: target AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: dleeuw at made-it dot com CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i686-linux-gnu GCC host triplet: i686-linux-gnu GCC target triplet: i686-linux-gnu I don't know for sure if this is a bug or intended but trying to build gcc with only c,c++,objc doesn't get met libffi. Enabling java also create libffi, configure values: configure --prefix=/usr/local/gcc-$DATE --enable-languages=c,c++,objc,java --enable-shared --enable-threads=posix --enable-nls --with-gnu-as --with-gnu-ld --without-included-gettext --with-system-zlib --enable-version-specific-runtime-libs --enable-objc-gc --enable-clocale=gnu --with-libffi I just tested it with gcc 3.3. On a Debian testing system.
next reply other threads:[~2003-07-24 12:24 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-07-24 12:24 dleeuw at made-it dot com [this message] 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=20030724122445.11660.dleeuw@made-it.com \ --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: linkBe 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).