Hi, Christopher Friedt schrieb: > On Wed, Oct 8, 2008 at 6:22 PM, Robert Schuster >> > PREFERRED_VERSION_jamvm-initial = "1.4.5" >>> (which does not exist in the package database) >>> PREFERRED_VERSION_classpath-initial = "0.93" >> What is the problem with jamvm-initial 1.4.5? > > That's so weird... I do nightly syncs, but when I checked a few days > ago in my copy of the repository there was no jamvm-initial_1.4.5.bb > recipe. > > I guess it's fine now .... although I've run into so many build > problems, I can't even begin to hope that 'bitbake jamvm' or 'bitbake > rxtx' will work... > > Thanks for the reply, I'll message again if all goes smoothly. Nice to hear, everything works now.
I also fixed the libtool problem of rxtx. There was another issue not being listed in any bug report I fixed as well: classpath-native is seemingly miscompiled by Debian's gcc 4.3.2. At least I got strange behavior with [VM]File.exists(). It returned true while there is no directory. The problem disappeared when I added a printf() into the native code. So I expected GCC is optimizing in a wrong way here. Declaring the respective variable 'volatile' made the error go away, too. Ah yes. All this trouble was causing spurious ".class file could not be created" error messages printed by ecj when compiling rxtx. I have seen the same error in other recipes too and hope that they are fixed as well now. Regards Robert
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Openembedded-users mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users
