SPIDER Compilation and Linking

CONTENTS

• EXECUTABLES
• LINKING
• COMPILING
• LIBRARIES
• DEBUG SPIDER

• EXECUTABLES

  SPIDER	Irix	processors	fft library
  spider3	6.*	R4***	sgi complib
  spider4	6.*	R5000,R8000,R10000	sgi complib
  spider4ns	6.*	R5000,R8000,R10000	native SPIDER
  spider4mp	6.*	R5000,R8000,R10000 with multiple proc.	sgi complib

• LINKING SPIDER You should only have to relink the SPIDER software if you wish to make your own modifications to SPIDER's linking parameters (e.g. changing libraries from dynamic to static). In the documention that follows SPIDER_DIR refers to the location of SPIDER on your system and a '?' inside a filenames refers to the suffix of one of the specific SPIDER distributions available e.g. 3, 4, 4ns, 4mp. The directory: SPIDER_DIR/src contains makefiles named Makefile? These makefiles can be used to compile the source code, place the object code in an object library, link the object code with SGI object libraries, and create an executable binary file. Use the following commands to save the original SPIDER executable as: spider?_orig and to relink SPIDER on your machine:

  cd SPIDER_DIR/src
  mv ../bin/spider? ../bin/spider?_orig
  make -f Makefile?
  

• Compiling and Linking the Executable If you wish to modify SPIDER source code or to compile SPIDER with different compilation options (e.g. use native SPIDER fft code instead of SGI's fft code or change optimization levels) you will have to compile the source code on your computer.
  Use the following commands to save the original object library under another name and compile and link all of SPIDER:

  cd SPIDER_DIR/src
  mv spider?.a spider?_orig.a
  make -f Makefile?
  

  If the make operation fails or the new executable does not run contact us at the address below.

  Notes: The archive ar command in the Makefile will use a lot of space in your TMPDIR. If you get a message about no space being left on your device I suggest you redefine TMPDIR to a directory that has space (e.g.):
  setenv TMPDIR /usr/tmp

• MAKEFILES

  SPIDER	Irix	processors	make	foc	focl
  spider3	6.*	R4***	make 3	foc -3	focl -3
  spider4	6.*	R5000,R8000,R10000	make 4	foc -4	focl -4
  spider4ns	6.*	R5000,R8000,R10000	make 4ns	foc -4ns	focl -4ns
  spider4mp	6.*	R5000,R8000,R10000 with multiple proc.	make 4mp	foc -4mp	focl -4mp

• debug SPIDER

  SPIDER	Irix	processors	make	focd	focld
  spider3d	6.*	R4***	maked 3	focd -3	focld -3
  spider4d	6.*	R5000,R8000,R10000	maked 4	focd -4	focld -4
  spider4mpd	6.*	R5000,R8000,R10000 with multiple proc.	maked 4mp	focd -4mp	focld -4mp

• Summary of Compilation and Linking Flags

  -DSP_UNIX	cpp flag for selective compilation on Unix
  -DSP_SUN4	cpp flag for selective compilation on Sun 4.* Unix
  -DSP_NT	cpp flag for selective compilation on NT
  -D__osf__	cpp flag for use on "OSF" Unix
  -DSP_R8000	cpp flag to set large memory availability
  -DSP_MP	cpp flag for selective compilation on multiprocessor SGI
  -DSP_DISTRIB	cpp flag for distributed code selection
  -DSP_LIBFFT	cpp flag for sgi. libfft use
  -O3	optimization level
  -mp	for parallel compilation & linking
  -mips2	target SGI architecture
  -mips3	target SGI architecture
  -mips4	target SGI architecture
  -32	32 bit code
  -n32	64 bit code with 32 bit addresses
  -bytereclen	record length in OPEN is in bytes
  -old_rl	record length in OPEN is in bytes
  -multigot	obscure segmentation stuff (faster than -xgot)
  xgot	obscure segmentation stuff
  -g	for debug use

• Auxiliary System DSO Libraries

  -lcomplib.sgimath	sgi libfft library
  -lcomplib.sgimath_mp	sgi parallel libfft library

  Static and dynamic library dependencies

  To see static dependencies (the names of libraries specified at compile time), use 'odump -Dl' or 'elfdump -Dl' for ELF format executables. Both are in the: dev.cmplrs_sw.util subsystem.
  example: elfdump -Dl spider4mp.1

  To see dynamic dependencies (the full paths to libraries determined at runtime, after environment variables are taken into account, which is what SunOS' 'ldd' tells you), use rld.debug and turn on rld tracing with _RLD_ARGS. See the rld(1) manpage.
  setenv _RLD_ARGS "-trace"
  setenv _RLD_PATH "/usr/lib/rld.debug"
  Then run the spider executable.

• BUGS, SUGGESTIONS In the event that you have questions about an operation or wish to report bugs please send us complete info on what you are trying to do, including relevant results files, procedure files, and error messages.

  Send such info to:

  ArDean Leith
  Wadsworth Labs, P.O. Box 509, Albany, New York 12201
  phone: 518-486-5604
  fax: 518-486-2191
  email: spider@wadsworth.org

  ---

  Source file: compiles.html     Updated: 1 December 1999     ArDean Leith