All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Veigl <chris@shifz.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: building classpath / ecj-initial fails
Date: Mon, 11 Jan 2010 20:57:13 +0000 (UTC)	[thread overview]
Message-ID: <loom.20100111T211613-99@post.gmane.org> (raw)
In-Reply-To: 20100111094046.GQ17224@jama

Martin Jansa <martin.jansa <at> gmail.com> writes:
> > ERROR: function do_compile failed
> > 

> git pull.. se my commit yesterday


I did a git pull, cleared the tmp folder and let 
bitbake run during the night, but get the same error:

  tmp/staging/i686-linux/usr/bin/java-initial -classpath  antlr.Tool -o \
    ../tools/generated/gnu/classpath/tools/gjdoc/expr/ \
    ./gnu/classpath/tools/gjdoc/expr/java-expression.g
  Unrecognised command line option: -o


must be something different ...
seems like jamvm version 1.4.5 does not have the "-o" switch !?

I currently use

  PREFERRED_VERSION_jamvm-initial = "1.4.5"
  PREFERRED_VERSION_classpath-initial = "0.93"

  PREFERRED_VERSION_jamvm-native = "1.5.3"
  PREFERRED_VERSION_classpath-native = "0.98"

  PREFERRED_VERSION_jamvm = "1.5.2"
  PREFERRED_VERSION_classpath = "0.98"

  PREFERRED_VERSION_libecj-bootstrap = "3.4"

as recommended in the openembedded wiki ...
regards,
chris.




  parent reply	other threads:[~2010-01-11 21:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-09 20:47 building classpath / ecj-initial fails Chris Veigl
2010-01-09 22:11 ` Henning Heinold
2010-01-11  9:27   ` Chris Veigl
2010-01-11  9:40     ` Martin Jansa
2010-01-11 14:18       ` Jaap de Jong
2010-01-11 15:51         ` dfoley
2010-01-11 19:01         ` Dallas Foley
2010-01-11 20:56           ` Chris Veigl
2010-01-11 20:57       ` Chris Veigl [this message]
2010-01-11 21:35         ` Martin Jansa
2010-01-12  0:03           ` Chris Veigl
2010-01-12  8:32           ` Chris Veigl

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=loom.20100111T211613-99@post.gmane.org \
    --to=chris@shifz.org \
    --cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.