Randy McMurchy wrote: > DJ Lucas wrote these words on 03/23/08 23:52 CST: >> Randy McMurchy wrote: >>> DJ Lucas wrote these words on 03/23/08 23:30 CST: >>> >>>> You don't by chance have gnu-sharutils installed do you? Did it find a >>>> uudecode (that doesn't come from JDK5)? This has bit a few people before. >>> I used to have it, but it appears the GMime installation replaced it. >>> >>> [EMAIL PROTECTED]: ~ > uudecode --version >>> uudecode - GMime 2.2.10 >>> >>> [EMAIL PROTECTED]: ~ > ls -l /usr/bin/uudec* >>> -rwxr-xr-x 1 root root 7544 Jul 20 2007 /usr/bin/uudecode >>> -rwxr-xr-x 1 root root 10024 Jul 2 2007 /usr/bin/uudecode.sharutils >>> >> I bet that is the problem then... > > Not sure. Here's relevant stuff from the BDB configure when it failed. > > checking for javac... javac > checking if javac works... yes > checking for jar... jar > checking for uudecode... yes > checking if uudecode can decode base 64 file... yes > checking if /opt/jdk/bin/java works... configure: error: The Java VM > /opt/jdk/bin/java failed (see config.log, check the CLASSPATH?) > dmake: Error code 1, while making > 'unxlngi6.pro/misc/build/so_configured_so_berkeleydb' > ---* tg_merge.mk *--- > > ERROR: Error 65280 occurred while making /mnt/rmldata1/scratch/berkeleydb > dmake: Error code 1, while making 'build_instsetoo_native' > > > > The config.log file pointed to Java issues with class exceptions. That > log file was overwritten so I'm going on memory now. It won't be hard > to reproduce though. Keep in mind the same thing is happening to > Robert. So it isn't something unique to me. It ought to be easy to > figure out. > > Here's after I changed to use JDK5 > > checking if javac works... yes > checking for jar... jar > checking for uudecode... yes > checking if uudecode can decode base 64 file... yes > checking if /opt/jdk/bin/java works... yes > checking for javac... /opt/jdk/bin/javac > checking absolute path of javac... /opt/jdk/bin/javac > checking java version... 1.5.0_12 > checking whether stat file-mode macros are broken... no >
The problem will hopefully disappear if uudecode is moved out of the way. (Warning: SWAG) You are using an old class file compiled against who knows which version of JDK that probably used some deprecated API. 6 probably ignores it or works around it. Basically, we need to check java version in configure and only use uudecode if minor version < 6 (Java2 SDK 1.6.0 == Java SE 6 marketing title). -- DJ Lucas -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
