public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "david dot griffiths at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug java/35923] gcj: error trying to exec 'ecj1': execvp: No such file or directory Date: Wed, 16 Apr 2008 14:32:00 -0000 [thread overview] Message-ID: <20080416143201.15998.qmail@sourceware.org> (raw) In-Reply-To: <bug-35923-16056@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from david dot griffiths at gmail dot com 2008-04-16 14:31 ------- Hi, made no difference. I created a separate gcc-4.3.0-build directory and placed the ecj.jar both in there and in the top level source director (just to be sure). Note that the build directory contains no libjava on completion, not sure if it should? (As that's the only place that seems to refer to ecj1). I am just doing "./configure" but that should build java by default, right? The config.log certainly contains lines like "build_configargs='--cache-file=../config.cache '--enable-languages=c,c++,fortran,java,objc' --program-transform-name='s,y,y,''". -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35923
next prev parent reply other threads:[~2008-04-16 14:32 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-04-13 16:30 [Bug java/35923] New: " david dot griffiths at gmail dot com 2008-04-13 23:59 ` [Bug java/35923] " brian at dessent dot net 2008-04-14 12:25 ` david dot griffiths at gmail dot com 2008-04-15 4:07 ` brian at dessent dot net 2008-04-16 14:32 ` david dot griffiths at gmail dot com [this message] 2008-04-16 14:50 ` brian at dessent dot net 2008-06-13 1:28 ` sebasmagri at gmail dot com 2009-02-03 8:43 ` cnstar9988 at gmail dot com 2009-03-03 16:23 ` norm at nebcs dot com 2009-05-28 20:59 ` jlquinn at optonline dot net 2010-02-17 15:24 ` davek 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=20080416143201.15998.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@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).