🚀 go-pugleaf

In article <280DD361.27063@ics.uci.edu> echarne@ics.uci.edu
(Eli B. Charne) writes:
   This is an annoying (but I suppose reasonable) problem with dynamically
   linked libraries in SunOS.

   If you run ldd on the binaries in the source dir, you will see that they are
   linked with relative paths.  You should find that moving the executables
   back into the dir they were compiled in (or for that matter any directory
   that deep in the tree) will make them work again.

   What I did was re-compile the 'bin' directory using "installed" path names
   instead of the relative path names.  (After installing everything else, I
   added:

	   #ifndef UseInstalled
	   #define UseInstalled YES
	   #endif

   to the local.def configuration file, and re-made the Makefiles for the bin
   directory using this.  (You also have to give path names to the installed
   binaries in the local.def config file)  This makes the binaries dynamically
   link with the full path name, so you can put the binaries wherever you like.

This is not necessary.  Yes, the the binaries are linked with relative
paths, but if you pay close attention to the command line used to link
the binaries, you'll see that the very last -L specifies an absolute
directory (ABSLIBDIR).  If you gave the correct path name to LibDir in
the local.def config file *before* making World, the binaries will be
linked with the correct absolute path name needed to find the
installed libraries.  When you install the binaries and libraries, the
the relative path names will no longer work as you mentioned but the
absolute path name *will* work.
-- 
John Interrante / interran@lurch.stanford.edu