[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Woody clobbers Blackdown!



I finally put a bullet in my teeth and dist-upgraded a potato system to woody.
In potato I had been running communicator-smotif with the Blackdown Java
plugin. Here's what I have now, post-upgrade:

communicator-base         4.73-19        Communicator base support
communicator-nethelp-473  4.73-19        Communicator online help 
communicator-smotif-473   4.73-19        Netscape Communicator 4.73 
communicator-spellchk     4.73-19        

netscape-base-4           4.75-2         Popular World-Wide-Web browser 
netscape-base-473         4.73-19        4.73 base support for netscape
netscape-java-473         4.73-19        Netscape Java support for version 
netscape-smotif-473       4.73-19        This installs a standard set of 

java-common               0.4            Base of all Java packages
j2sdk1.3                  1.3.0-2        Blackdown Java(TM) 2 SDK

SO, starting netscape now, I get the following:

--- begin nfg snip ---

INTERNAL ERROR on Browser End: Could not load
/usr/lib/j2re1.3/lib/i386/libjavaplugin_oji.so: linking error=undefined
symbol: PR_GetCurrentThread

System error?:: Success

--- end-nfg-snip ---

How to resolve this? Somehow Woody has put the kibosh on Blackdown java.
Here's one more piece of data, ldd on the above-cited libjavaplugin_oji.so:

bash-2.04$ ldd /usr/lib/j2re1.3/lib/i386/libjavaplugin_oji.so
	libgdk-1.2.so.0 => /usr/lib/libgdk-1.2.so.0 (0x4005c000)
	libBrokenLocale.so.1 => /lib/libBrokenLocale.so.1 (0x40090000)
	libc.so.6 => /lib/libc.so.6 (0x40092000)
	libgmodule-1.2.so.0 => /usr/lib/libgmodule-1.2.so.0 (0x40199000)
	libglib-1.2.so.0 => /usr/lib/libglib-1.2.so.0 (0x4019d000)
	libdl.so.2 => /lib/libdl.so.2 (0x401bf000)
	libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x401c2000)
	libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x401ca000)
	libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x401d8000)
	libm.so.6 => /lib/libm.so.6 (0x402a3000)
	/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)

I'm guessing that one of these is supposed to define "PR_GetCurrentThread" but
doesn't anymore since the upgrade?

TIA for any light shed on these murky precincts!




--
Bob Bernstein                  http://www.ruptured-duck.com




Reply to: