public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jlpoole at pon dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug java/42409] org.eclipse.jdt.internal.compiler.batch.GCCMain not found Date: Sun, 03 Jan 2010 18:43:00 -0000 [thread overview] Message-ID: <20100103184309.2842.qmail@sourceware.org> (raw) In-Reply-To: <bug-42409-18569@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from jlpoole at pon dot net 2010-01-03 18:43 ------- Here's my configuration log: plug build # pwd /mnt/seagate2/download/gnu/build plug build # head config.log This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by configure, which was generated by GNU Autoconf 2.64. Invocation command line was $ ../trunk/configure --enable-languages=java ## --------- ## ## Platform. ## plug build # -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42409
next prev parent reply other threads:[~2010-01-03 18:43 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-12-17 17:54 [Bug java/42409] New: " jlpoole at pon dot net 2009-12-24 16:23 ` [Bug java/42409] " jlpoole at pon dot net 2010-01-03 18:21 ` jlpoole at pon dot net 2010-01-03 18:23 ` jlpoole at pon dot net 2010-01-03 18:30 ` jlpoole at pon dot net 2010-01-03 18:43 ` jlpoole at pon dot net [this message] 2010-01-03 18:56 ` jakub at gcc dot gnu dot org 2010-01-04 1:51 ` jlpoole at pon dot net 2010-01-04 11:33 ` ramana at gcc dot gnu dot org 2010-01-04 14:21 ` jakub at gcc dot gnu dot org 2010-01-05 2:31 ` jlpoole at pon dot net 2010-01-05 2:35 ` jlpoole at pon dot net 2010-01-07 14:27 ` jlpoole at pon dot net 2010-03-20 0:10 ` ramana 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=20100103184309.2842.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: 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).