Re: [Swarm-Support] Compiling Swarm-2.2 on Solaris 2.8

[Marcus G. Daniels]

Gary Polhill wrote:
> If someone knows how to create binaries on Solaris and it's not difficult, I 
> could do that too--but presumably there are issues with paths to various bits 
> of needed software?
>   
Long ago, we had packages for the pkgadd program in Solaris. Such 
packages get installed in known directories in /opt, so the idea is to 
hardcode the paths in the Swarm configuration.

> Moving on, I can get heatbugs to compile and run, but now have the following 
> problems:
>
> (a) I can compile jheatbugs, but when I run it I get this:
>
> % javaswarm StartHeatbugs
> This is StartHeatbugs.main().
> Exception caught: no javaswarm in java.library.path
> Exception in thread "main" java.lang.UnsatisfiedLinkError: createBegin
>         at swarm.SwarmEnvironmentCImpl.createBegin(Native Method)
>         at swarm.Globals.<clinit>(Globals.java:39)
>         at StartHeatbugs.main(StartHeatbugs.java:161)
>
> Is there something I need to put in my environment? (PATH contains 
> $SWARMHOME/bin)
>   
Strange, the javaswarm script should have dealt with that.   All it does 
is set LD_LIBRARY_PATH to where libjavaswarm.so is installed and 
CLASSPATH to include the full path of swarm.jar and kawa.jar.

> (b) When I compile my own model, I get the following error when I run it:
>
> % ./model0-8-3
> Assertion failed: __objc_class_hash, file 
> ../../../src/20060612/swarm/libobjc/class.c, line 130
> Abort
>   
Hmm,  I don't remember if recent version of GCC / Solaris fix this, but 
once upon a time if you had a GCC configured with the native linker, the 
constructors for Objective C wouldn't get called, and you'd get a 
failure like this.  The fix was to build GNU binutils to gets its 
linker, and then build GCC to use that.