GMime version of uudecode breaks OOo/BDB Java build

[Randy McMurchy]

It has been determined that the version of uudecode installed by the current book's GMime package breaks the Berkeley DB build if you pass --enable-java to the BDB build, or if an OOo build needs to build the BDB Java library.

The fix is to not use GMime's uudecode. The GNU Sharutils version of uudecode presents no issues. It was also determined that if you pass

uudecode="no"

before the configure command in BDB it will work, but it will have to rebuild some stuff in the BDB tree (takes a few extra seconds).

The OOo issue is a bit more complex and may require a sed/patch to pass this argument before beginning the build.

[Randy McMurchy]

I forgot to mention that this issue only occurs if you have JDK6 installed. A JDK5 installation works with the GMime uudecode.

Only passing this info along as FYI.

[Randy McMurchy]

I added a note to the Berkeley DB instructions notifying readers about the conflict, a couple of methods for how to determine if the conflict exists, and what to do if there is a conflict. The base DB instructions didn't change (I felt that the amount of folks that would actually rebuild BDB with Java support was rather small).

The ticket will be left open until something is done to the OOo instructions.

[Randy McMurchy]

OpenOffice instructions were fixed in BLFS commit r7367. This completes all the issues in the ticket.