Closed Bug 198471 Opened 22 years ago Closed 22 years ago

Java Plugin does't load: Failed to initialize shared library

Categories

(Core Graveyard :: Plug-ins, defect)

x86
Linux
defect
Not set
major

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 116444

People

(Reporter: Nikolaus, Assigned: peterlubczynski-bugs)

Details

Attachments

(2 files)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030320 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030320 I'm unable to install a java 1.4 plugin into mozilla. I compiled mozilla for myself using gcc 3.2 and the cvs version tagged MOZILLA_3_0_RELEASE. My buildparams were: [See attachment #1 [details] [diff] [review]] I first tried to download the plugin using the automatic installation. But after the download was finished, nothing happened. I had to kill mozilla. No files had been installed. Then I tried it with Sun J2SDK 1.4.0 it Sun J2SDK1.4.1, symlinking the .so in jre/plugin/i386/ns610/ into ~/.mozilla/plugins. This resulted in the following error on start and when accessing about:modules: LoadPlugin: failed to initialize shared library /usr/lib/j2se/1.4/jre/plugin/i386/mozilla/javaplugin_oji.so [/usr/lib/j2se/1.4/jre/plugin/i386/mozilla/javaplugin_oji.so: undefined symbol: GetGlobalServiceManager__16nsServiceManagerPP17nsIServiceManager] Then I heard that a gcc 3.2 mozilla doesn't mix well with the gcc 2.95 compiled sun jdks. Therefore I tried it with Blackdown Java (they use gcc 3.2). Here i symlinked the file in plugin/mozilla. The error was the same as with the sun jdk. At last, i tried to compile mozilla using gcc 2.95. But make stops with: [ See attachment #2 [details] [diff] [review]] and i had to call ./configure with --disable-pedantic before: --snip-- checking whether C++ compiler has -pedantic long long bug... yes configure: error: Your compiler appears to have a known bug where long long is miscompiled when using -pedantic. Reconfigure using --disable-pedantic. --snip-- Reproducible: Always Steps to Reproduce: 1. Compile Mozilla with gcc 3.x (or use an actual debian unstable package)) 2. Symlink the java plugin library into the plugin directory (you can use either Sun JDKs or Blackdown JDKs) 3. Start mozilla 4. Load about:plugins Actual Results: Mozilla didn't list the java plugin. I'm unable to run applets (i'm recommended to download the plugin). I got the following message on the console: LoadPlugin: failed to initialize shared library /usr/lib/j2se/1.4/jre/plugin/i386/mozilla/javaplugin_oji.so [/usr/lib/j2se/1.4/jre/plugin/i386/mozilla/javaplugin_oji.so: undefined symbol: GetGlobalServiceManager__16nsServiceManagerPP17nsIServiceManager] Expected Results: It should have loaded the module, of course. :-)
Attached file My build params (deleted) —
Attached file build log using gcc 2.95 (deleted) —
Mozilla compiled with gcc 3.2 and JRE from sun ? Duplicate of bug 197360 : Java plugin not recognised See Comment #3 (same problem as RPM compiled with GCC 3.2) and comment #5 and 6. Marking this bug as duplicate of 197360. Feel free to reopen it if you disagree. *** This bug has been marked as a duplicate of 197360 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Summary: Java Plugin does't load: Failed to initialize shared library → Java Plugin does't load: Failed to initialize shared library
Hello! I tried it with Blackdown SDK (compiled with gcc 3.2). The same error occurs. But i already wrote that in my first description. I don't know who you marked this bug a duplicate. I repeat: The issue is *not* solved by using a JDK compiled with gcc 3.2.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Bug 116444 is actually the main bug about java and gcc 3.2. Bug 197360 is best read as being about the RH 8.0 RPM. The build log (2nd attachment) shows gcc bombing on the -fshort-wchar option. This option is only used after being tested during configure. The most likely explanation here is that you configured using gcc 3.x, then tried to compile with gcc 2.x without running configure again. The gcc 3.2 build of the blackdown java plugin doesn't contain a reference to the symbol "GetGlobalServiceManager__16nsServiceManagerPP17nsIServiceManager". The gcc 2.9x version does, and of course so does sun's java. I find it hard to believe you got an error about that symbol while trying to used the gcc 3.2 version of blackdown with a gcc 3.2 version of mozilla. This report is really about three separate issues, which makes it tough to handle properly. I'm going to resolve this as a dupe of bug 116444 based on the sun java issue. If you are still experiencing problems with blackdown java after double-checking everything, you should open a separate bug report specifically about that. *** This bug has been marked as a duplicate of 116444 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago22 years ago
Resolution: --- → DUPLICATE
Marking Verified Duplicate
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: