[Bug 4588] New: 'bitbake rxtx' fails on jamvm-initial and then classpath-native
bugzilla-daemon at amethyst.openembedded.net
bugzilla-daemon at amethyst.openembedded.net
Tue Sep 30 14:00:43 UTC 2008
http://bugs.openembedded.net/show_bug.cgi?id=4588
Summary: 'bitbake rxtx' fails on jamvm-initial and then
classpath-native
Classification: Unclassified
Product: Openembedded
Version: Angstrom 2008.x
Platform: ARM
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component: org.openembedded.dev
AssignedTo: openembedded-issues at lists.openembedded.org
ReportedBy: chrisfriedt at gmail.com
Created an attachment (id=10416)
--> (http://bugs.openembedded.net/attachment.cgi?id=10416)
OpenOffice.org spreadsheet error / resolution details
This bug is always reproducible.
================== Resolution Summary ================
== jamvm-initial ==
Fails saying 'libffi.so.5: no such file or directory'
Created jamvm-initial_1.5.1.bb and jamvm-initial_1.5.1.patch (see attached
.ods, error # 1, resolution details #1 & #2)
== classpath-native ==
Needed to manually edit the 'java-initial' script in ${STAGEDIR}/usr/bin -
should probably be updated somewhere in the openembedded scripts themselves.
Reason:
The 'java-initial' script has special requirements when using 'jamvm-initial'
as the JRE. This is due to JamVM's unusual treatment of the '-bootclasspath'
argument (or rather its lack of treatment). JamVM accepts '-Xbootclasspath'
instead. the directory with 'libjava*.so', which are all provided by JamVM,
also needs to be specified with LD_LIBRARY_PATH.
======================================================
In order to reproduce this error:
1. Follow the 'Getting Started' instructions here:
http://wiki.openembedded.net/index.php/Getting_Started
2. Create the configuration file ${HOME}/beagleboard/build/conf/local.conf (See
attachment 'local.conf')
3. Run 'bitbake rxtx'
Cheers,
Chris
--
Configure bugmail: http://bugs.openembedded.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Openembedded-issues
mailing list