swarm-support
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

building swarm on sun network or using precompiled binaries...


From: Paul Box
Subject: building swarm on sun network or using precompiled binaries...
Date: Fri, 29 Oct 1999 10:36:55 -0600 (MDT)

Hello everyone

I have been trying (once again) to build swarm on our sun network
here, to transfer work away from my personal linux box.  A hard disk
failure on the linux box has helped my initiative in this :0

I have tried using the precompiled binaries, but there seems to be a
problem there-- the binary distributions are designed to be unpacked
in an /opt/SDGswarm/ directory, which (as I understand it) is fine if
you intend to use swarm on just that one computer.  Here we have more
than 100 suns linked together through automounters and the like, with
the intent that resources be shared as much as possible between
machines.  In order to have the swarm libraries available to all the
computers, they need to be placed in one of the directories visible to 
everyone.


<<<building headbugs with the precompiled binaries>>>

I unpacked the libraries for sparc-solaris-2.7, and tried copying
everything from their /opt/SDGswarm/ directories to /auto/d2/gnu (the
public place for gnu software); I had to do some edits to all the
files in etc/swarm to make sure that they refer to files in the new
locations.  I then tried to build heatbugs to make sure that
everything worked.  When I run 'make', I get a lot of complaints about
things not being in the /opt/SDGswarm directories, as well as warnings
that the libraries have been moved.  Some of this is addressed in
libtool-swarm, and some specified in the various lib*.la; I could
feasibly go through and edit all of those files to reflect their new
home in the /auto/d2/gnu directory, but I started to think that simply
doing a build from scratch was the cleanest altertnative.  


<<< Trying to build the swarm libraries from scratch >>>

My first attempts at building the swarm distribution failed because I
had inconsistent versions of gcc binaries and libraries.  I upgraded
everything to gcc 2.93, updated xpm.h, hdf5, tcl, tk, and emacs to the 
newest versions I could find, and installed jdk, and tried the build
again.  This time, I got the following output during the build:

[...stuff deleted...]
make[3]: Leaving directory `/auto/sanduku/apps/swarm-2.0.1/src'
make[2]: Leaving directory `/auto/sanduku/apps/swarm-2.0.1/src'
Making all in java
make[2]: Entering directory `/auto/sanduku/apps/swarm-2.0.1/java'
cp -f ../etc/common.el /auto/sanduku/apps/swarm-2.0.1/_common.el
TOP_BUILDDIR=/auto/sanduku/apps/swarm-2.0.1/
BUILDDIR=/auto/sanduku/apps/swarm-2.0.1/java /auto/d2/gnu/bin/emacs
-batch -f batch-byte-compile /auto/sanduku/apps/swarm-2.0.1/_common.el
Wrote /auto/sanduku/apps/swarm-2.0.1/_common.elc
Done
mv /auto/sanduku/apps/swarm-2.0.1/_common.elc
/auto/sanduku/apps/swarm-2.0.1/common.elc
rm -f /auto/sanduku/apps/swarm-2.0.1/_common.el
cp -f ../etc/protocol.el /auto/sanduku/apps/swarm-2.0.1/_protocol.el
TOP_BUILDDIR=/auto/sanduku/apps/swarm-2.0.1/
BUILDDIR=/auto/sanduku/apps/swarm-2.0.1/java /auto/d2/gnu/bin/emacs
-batch -f batch-byte-compile
/auto/sanduku/apps/swarm-2.0.1/_protocol.el
Loading cl-extra...
Wrote /auto/sanduku/apps/swarm-2.0.1/_protocol.elc
Done
mv /auto/sanduku/apps/swarm-2.0.1/_protocol.elc
/auto/sanduku/apps/swarm-2.0.1/protocol.elc
rm -f /auto/sanduku/apps/swarm-2.0.1/_protocol.el
cp -f java-stub.el ./_java-stub.el
TOP_BUILDDIR=/auto/sanduku/apps/swarm-2.0.1/
BUILDDIR=/auto/sanduku/apps/swarm-2.0.1/java /auto/d2/gnu/bin/emacs
-batch -f batch-byte-compile
/auto/sanduku/apps/swarm-2.0.1/java/_java-stub.el
Wrote /auto/sanduku/apps/swarm-2.0.1/java/_java-stub.elc
Done
mv ./_java-stub.elc java-stub.elc
rm -f ./_java-stub.el
SWARMSRCDIR='.' TOP_BUILDDIR=/auto/sanduku/apps/swarm-2.0.1/
BUILDDIR=/auto/sanduku/apps/swarm-2.0.1/java /auto/d2/gnu/bin/emacs
-batch -l /auto/sanduku/apps/swarm-2.0.1/java/java-stub.elc -f
java-run-all-unicode
Wrong type argument: char-or-string-p, nil
make[2]: *** [Makefile.common] Error 255
make[2]: Leaving directory `/auto/sanduku/apps/swarm-2.0.1/java'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/auto/sanduku/apps/swarm-2.0.1'
make: *** [all-recursive-am] Error 2


If I type 'make' again at the command line to restart things, I get
the following output:

make[3]: Leaving directory `/auto/sanduku/apps/swarm-2.0.1/src'
make[2]: Leaving directory `/auto/sanduku/apps/swarm-2.0.1/src'
Making all in java
make[2]: Entering directory `/auto/sanduku/apps/swarm-2.0.1/java'
make -C c all
make[3]: Entering directory `/auto/sanduku/apps/swarm-2.0.1/java/c'
cat  > collections_stubs.m


At this point the program hangs, I guess since it's trying to cat
'nothing' into collections_stubs.m.


So, I have two questions:  
        1- what is going wrong with the build? 
        2- is there a simple way to use the precompiled binaries
                in a directory other than /opt/SDGswarm/ ?

Pardon the rambling nature of this post.

-- 
//////////////////////////////////////////////////
// Dr. Paul Box
// Dept of Geography and Earth Resources
// UMC 5240
// Utah State University      http://www.nr.usu.edu/~sanduku
// Logan, UT  84321           Phone: 435-797-2546
//////////////////////////////////////////////////

*  If Elvis was so great, why was he buried in the back yard like a
*  hamster?

                  ==================================
   Swarm-Support is for discussion of the technical details of the day
   to day usage of Swarm.  For list administration needs (esp.
   [un]subscribing), please send a message to <address@hidden>
   with "help" in the body of the message.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]