bug / missing sys call?

[Gary Aitken]

Hate to bother you, but I'm trying to get eclipse-cdt running on fbsd 9.1 and 
have an issue I'm not sure how to pursue.

When eclipse-cdt is run and one first hits the debug compile button, 
the following trace shows up on the controlling shell:

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)
...
<snip>

The last class (ProcessFactory) is in
  /usr/local/lib/eclipse/plugins/org.eclipse.cdt.core_5.1.2.201002161416.jar
and appears to be a missing hook into to the core fbsd system.

I'm not sure I can get myself up to speed enough to do anything about this,
but can you tell me:

What is the state of the base eclipse port?  I now see it is quite a ways
behind the latest release.  I also see there is no maintainer for eclipse-cdt;
not sure if I'm up for that be we'll see.

Thanks,

Gary