Bug 159882 - UnsatisfiedLinkError: libspawner
UnsatisfiedLinkError: libspawner
Product: Fedora
Classification: Fedora
Component: eclipse-cdt (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Andrew Overholt
Depends On:
  Show dependency treegraph
Reported: 2005-06-08 16:08 EDT by Andrew Overholt
Modified: 2007-11-30 17:11 EST (History)
0 users

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

Attachments (Terms of Use)
stack trace echoed to console (2.03 KB, text/plain)
2005-06-08 16:08 EDT, Andrew Overholt
no flags Details

  None (edit)
Description Andrew Overholt 2005-06-08 16:08:06 EDT
Description of problem:
When starting a new CDT project, the UnsatisfiedLinkError is shown on the
console from which you launched eclipse.

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

How reproducible:

Steps to Reproduce:
1. start eclipse
2. File->New->Project->C->Managed C Project
3. finish the wizard
Actual results:
see attached stack trace

Expected results:
Nothing echoed to the console

Additional info:
I'm not sure if this is actually affecting anything negatively as things mostly
appear to work.
Comment 1 Andrew Overholt 2005-06-08 16:08:06 EDT
Created attachment 115238 [details]
stack trace echoed to console
Comment 2 Tom Tromey 2005-07-03 14:05:32 EDT
As I recall libspawner is used by the CDT for running
other programs.  I forget if it is needed for gdb or if it is
also used for things like make.

Anyway, at least in 3.0 (I didn't look at 3.1), it should not be
missing.  This ought to be easy to fix... make sure it is built
(see org.eclipse.cdt.core.linux) and make sure it is installed
and packaged properly.
Comment 3 Andrew Overholt 2005-10-21 16:24:01 EDT
This should be fixed with 3.0.0; I see libspawner.so.  Closing unless/until
someone sees the same error again.

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