On 3Jul, Juergen Kreileder wrote: > Mark S. Petrovic <[EMAIL PROTECTED]> writes: > > > I've recently been experimenting with Blackdown JMF under Suse 7.3 > > Linux. While I have had good results with the Sun JRE v1.3, I have > > not had success with the same code in the same environment under > > JRE v1.4. The requirements page for Blackdown JMF indicate that > > a JRE > 1.3.0 is required. Perhaps this meant at the time "greater > > than 1.3.0, but implicitly less than 1.4". > > > > [...] > > > The first sign of trouble, having detected an H261/RTP stream, is > > > > java.lang.UnsatisfiedLinkError: JMFSecurityManager: >java.lang.UnsatisfiedLinkError: /nfs/petr > > ovic/share/java/jmf/jmf-2.1.1/lib/libjmfjawt.so: >/nfs/petrovic/share/java/jmf/jmf-2.1.1/lib/l > > ibjmfjawt.so: undefined symbol: JAWT_GetAWT > > Does it work if you set > LD_LIBRARY_PATH=<path to 1.4jre>/lib/i386:<path to 1.4 jre>/lib/i386/client > and LD_PRELOAD=<path to 1.4 jre>/lib/i386/libjawt.so ?
Taking your suggested LD_LIBRARY_PATH and appending to it the directory in which the JMF-specific shared libraries are stored results in the application in question indeed running under a 1.4 JRE. Also assigned and exported was the value of LD_PRELOAD you suggest. Why must LD_LIBRARY_PATH contain these explicit path components under JRE v1.4, but not under JRE 1.3? Why must libjawt.so be preloaded? Thanks. > Juergen > > -- > Juergen Kreileder, Blackdown Java-Linux Team > http://www.blackdown.org/java-linux.html ---------------------------------------------------------------------- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
