Eclipse Community Forums: C / C++ IDE (CDT) » CDT debug compile; no spawner in java.library.path

Home » Language IDEs » C / C++ IDE (CDT) » CDT debug compile; no spawner in java.library.path(What is the spawner and where should it be? FreeBSD 9.1, /usr/ports install)

Show: Today's Messages :: Show Polls :: Message Navigator

CDT debug compile; no spawner in java.library.path [message #1109131]

Sun, 15 September 2013 00:12

Gary Aitken

Messages: 11
Registered: July 2009

Junior Member

When I start CDT, it comes up ok with project source displayed.
If I click on the debug compile button, I see the following message in the shell window from which eclipse was started:

java.lang.UnsatisfiedLinkError: no spawner in java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1681)
at java.lang.Runtime.loadLibrary0(Runtime.java:840)
at java.lang.System.loadLibrary(System.java:1047)
at org.eclipse.cdt.utils.spawner.ProcessFactory.<init>(ProcessFactory.java:39)
at org.eclipse.cdt.utils.spawner.ProcessFactory.getFactory(ProcessFactory.java:51)
at org.eclipse.cdt.core.CommandLauncher.execute(CommandLauncher.java:151)
at org.eclipse.cdt.managedbuilder.internal.buildmodel.CommandBuilder.build(CommandBuilder.java:165)
at org.eclipse.cdt.managedbuilder.internal.buildmodel.StepBuilder.build(StepBuilder.java:93)
at org.eclipse.cdt.managedbuilder.internal.buildmodel.DescriptionBuilder$BuildStepVisitor.visit(DescriptionBuilder.java:91)
at org.eclipse.cdt.managedbuilder.buildmodel.BuildDescriptionManager.doAccept(BuildDescriptionManager.java:148)
at org.eclipse.cdt.managedbuilder.buildmodel.BuildDescriptionManager.doAccept(BuildDescriptionManager.java:156)
at org.eclipse.cdt.managedbuilder.buildmodel.BuildDescriptionManager.doAccept(BuildDescriptionManager.java:130)
at org.eclipse.cdt.managedbuilder.buildmodel.BuildDescriptionManager.accept(BuildDescriptionManager.java:124)
at org.eclipse.cdt.managedbuilder.internal.buildmodel.DescriptionBuilder.build(DescriptionBuilder.java:158)
at org.eclipse.cdt.managedbuilder.internal.core.CommonBuilder.invokeInternalBuilder(CommonBuilder.java:1027)
at org.eclipse.cdt.managedbuilder.internal.core.CommonBuilder.invokeBuilder(CommonBuilder.java:1786)
at org.eclipse.cdt.managedbuilder.internal.core.CommonBuilder.build(CommonBuilder.java:834)
at org.eclipse.cdt.managedbuilder.internal.core.CommonBuilder.build(CommonBuilder.java:589)
at org.eclipse.cdt.managedbuilder.internal.core.CommonBuilder.build(CommonBuilder.java:538)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374)
at org.eclipse.core.internal.resources.Workspace.buildInternal(Workspace.java:513)
at org.eclipse.core.internal.resources.Workspace.build(Workspace.java:432)
at org.eclipse.ui.actions.BuildAction$1.runInWorkspace(BuildAction.java:305)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

The compile seems to work, and reports various errors, etc.

What's the spawner that's missing and where should it be?

This is on a FreeBSD 9.1 system, with eclipse and CDT built from the ports subtree.

Report message to a moderator

Re: CDT debug compile; no spawner in java.library.path [message #1109590 is a reply to message #1109131]

Sun, 15 September 2013 17:27

Gary Aitken

Messages: 11
Registered: July 2009

Junior Member

This is caused by a missing (not yet written) set of system interface code for FreeBSD.
The relevant code is in jar files like:

org.eclipse.cdt.core.macosx.source_5.1.0.201002161416.jar (C and Java source code)
org.eclipse.cdt.core.macosx_5.1.0.201002161416.jar (Java classes and C runtime libraries)
presumably for the above C source

Question for core developers:

The Freebsd port appears to currently be using a relatively old (Indigo, 3.7) version of eclipse.
Am I correct in assuming that the above interface is likely to be the same in more current versions, assuming the os internals haven't changed?

[Updated on: Sun, 15 September 2013 17:40]

Report message to a moderator

Previous Topic:	Problem Building Linking to Exe Files?
Next Topic:	Adding MinGW GCC's include path to Eclipse installation on Windows 7

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 05:47:39 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter