From: Jaap de Jong <jaap.dejong@nedap.com>
To: openembedded-devel@lists.openembedded.org
Subject: java -cacao issues
Date: Fri, 23 Jul 2010 10:06:01 +0200 [thread overview]
Message-ID: <4C494D69.5010807@nedap.com> (raw)
Hi,
Finally I've been able to build for at91sam9263ek without any errors...
$ git log | head
commit ebc2e1d43afa43877c29bc47c87f38792a791bd8
Author: Martin Jansa <Martin.Jansa@gmail.com>
Date: Mon Jul 19 13:14:06 2010 +0200
linux-openmoko-2.6.32: add missing patch, enable XFS, brtfs, GPT
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
The following results on the target:
# java -version
Warning: no leading - on line 43 of
`/usr/lib/jvm/java-6-openjdk/jre/lib/arm/jvm.cfg'
Warning: missing VM type on line 43 of
`/usr/lib/jvm/java-6-openjdk/jre/lib/arm/jvm.cfg'
Warning: no leading - on line 43 of
`/usr/lib/jvm/java-6-openjdk/jre/lib/arm/jvm.cfg'
Warning: missing VM type on line 43 of
`/usr/lib/jvm/java-6-openjdk/jre/lib/arm/jvm.cfg'
java version "1.6.0_18"
OpenJDK Runtime Environment (IcedTea6 1.8) (6b18-1.8)
OpenJDK Shark VM (build 14.0-b16, mixed mode)
After removing the trailing newline from
/usr/lib/jvm/java-6-openjdk/jre/lib/arm/jvm.cfg the warnings are gone:
# java -version
java version "1.6.0_18"
OpenJDK Runtime Environment (IcedTea6 1.8) (6b18-1.8)
OpenJDK Shark VM (build 14.0-b16, mixed mode)
# java -version -shark
java version "1.6.0_18"
OpenJDK Runtime Environment (IcedTea6 1.8) (6b18-1.8)
OpenJDK Shark VM (build 14.0-b16, mixed mode)
# java -version -cacao
LOG: [0x4001ec80] md_signal_handler_sigill: Unknown illegal
instruction 0xed1c5a06 at 0x441dc790
LOG: [0x4001ec80] Aborting...
Aborted
cacao crashes...
Any ideas?
Jaap de Jong
next reply other threads:[~2010-07-23 8:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 8:06 Jaap de Jong [this message]
2010-07-23 10:14 ` java -cacao issues Henning Heinold
2010-07-23 14:39 ` Xerxes Rånby
2010-07-27 7:22 ` Jaap de Jong
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=4C494D69.5010807@nedap.com \
--to=jaap.dejong@nedap.com \
--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.