Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 159031 - eclipse is unable to find libxpcom.so
eclipse is unable to find libxpcom.so
Product: Fedora
Classification: Fedora
Component: eclipse (Show other bugs)
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Andrew Overholt
: 159030 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2005-05-27 17:40 EDT by Bill Nottingham
Modified: 2014-03-16 22:54 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-08-24 10:54:12 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bill Nottingham 2005-05-27 17:40:28 EDT
Description of problem:

On startup, eclipse prints:

ls: /usr/lib/mozilla-*/libxpcom.so: No such file or directory
ls: /usr/lib/firefox-*/libxpcom.so: No such file or directory
dirname: too few arguments

Version-Release number of selected component (if applicable):


How reproducible:

Every time

Steps to Reproduce:
1. run eclipse

Additional info:

Of course, on x86_64, those would be in /usr/lib64.
Comment 1 Bill Nottingham 2005-05-27 17:42:56 EDT
*** Bug 159030 has been marked as a duplicate of this bug. ***
Comment 2 Jeroen Beerstra 2005-08-07 21:48:35 EDT
Same here (also on x86_64 ofcourse), perhaps this is related to:

Plug-in "org.eclipse.swt.gtk" version "3.1.0" referenced by this feature is missing.

And some other messages like that: mentioned software seems to be available and
is not part of a separate rpm. Looks like the Eclipse shipped with FC4 x86_64 is
partially broken.

I'll file a separate bug report, it just seems to me all these messages are
related and probably easy to fix. 

Comment 3 Andrew Overholt 2005-08-24 10:54:12 EDT
I just committed a fix for this to rawhide.  When I finally get bug #151832
sorted out, I'll do an FC4 update that includes this fix.

Note You need to log in before you can comment on or make changes to this bug.