Weren't you just complaining about how hard it was to perform configuration management of Java applications? :) Static linking is probably the simplest solution, but since that has been ruled out, you aren't left with much. I've run into similar issues with the Java Development Kit in the past. At one time the JDK was linked against an ancient version of libstdc++ that was not binary compatible with newer versions. This caused some stability problems with a JNI shared library I was developing that was linked against the a newer version of libstdc++. I believe I solved my problem by statically linking to libstdc++. Unfortunately, I do not know how to solve this problem without static linking. I think you are stuck creating a binary package for every version of every distro you want to support, complete with all the proper dependency metadata. This endaevor will lead you into the dark corners of the APT, RPM, and .deb package tools. Have fun! _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota Help beta test TCLUG's potential new home: http://plone.mn-linux.org Got pictures for TCLUG? Beta test http://plone.mn-linux.org/gallery tclug-list at mn-linux.org https://mailman.real-time.com/mailman/listinfo/tclug-list