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:56:46 +0000 (UTC) [thread overview]
Message-ID: <loom.20100111T215259-536@post.gmane.org> (raw)
In-Reply-To: 4B4B759D.3040609@techsol.ca
Dallas Foley <dfoley <at> techsol.ca> writes:
>
> Jaap de Jong wrote:
> > Hi Henning,
> >
> > My approach after many unsuccessful attempts:
> >
> > - install
> > apt-get install sun-java6-jdk
> > - edit local.conf
> > ASSUME_PROVIDED += " ecj-initial "
> > ASSUME_PROVIDED += " virtual/java-initial "
> > ASSUME_PROVIDED += " virtual/java-native "
> > ASSUME_PROVIDED += " virtual/javac-native "
> > PREFERRED_PROVIDER_classpath = "classpath"
> > PREFERRED_VERSION_classpath = "0.97.2"
> > - bitbake cacao
> >
thank you for the hint - i will try this next
> > Could not get jamvm nor classpath 0.98 compiled.
what problems did arise ?
>
> Not sure if this is the right answer, but I also could not build ecj-initial
> until I changed "-Xmx1024m" to "-Xmx512m" in recipes/ecj/files/ecj.in
> and I think rebuilding ecj-bootstrap-native and ecj-initial worked for me.
>
I suppose this solves the memory error in the "classpath - configure" - task.
which setup (in terms of PREFERRED_PROVIDER, PREFERRED_VERSION, ASSUME_PROVIDED)
did you use ? - and: could you build jamvm and classpath successfully ?
Using the OE-wiki setup, I got problems with the "compile" task (jamvm does not
recognize option "-o"), which do not relate to the above memory problems.
regards,
chris.
next prev parent reply other threads:[~2010-01-11 20:59 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 [this message]
2010-01-11 20:57 ` Chris Veigl
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.20100111T215259-536@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox