🚀 go-pugleaf

In <NISHIO.91Apr18054445@mizar.kuis.kyoto-u.ac.jp> nishio@kuis.kyoto-u.ac.jp (Nishio `Cchwitz' Shuichi) writes:


>I have just compiled 3.0 beta. However, I got some problems.

>1. I couldn't link ibuild, lacking _waitpid. Is this something new to
>  SunOS 4.1? 

>2. After I did "make install", when I try to execute commands such as
>  doc, I got the following message :

>	ld.so: libOS.so.3: not found 

>   They ran all right in the source tree, so I think this has
>  something to do with the dynamic linking, but unfortunately I have
>  no idea what to do.

  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.

  If you have plenty of disk space, you might even want to link the binaries
  staticlly (ad -Bstatic to the linker flags)...


>3. And finally, when I run doc on my SparcStation Console, it appears
>  with black-background and white-letters. Is this the right way?

  Hmm, mine comes up black on white (unless I do doc -rv).  It is quite a bit
  different than the alpha version was though.  Namely, it only has a File and
  Edit menu...

>I am working on a SparcStation with SunOS 4.0.3, using AT&T C++ 2.0 .

  I'm running on a Sparc running 4.1

-- 
      echarne@ics.uci.edu     // \\    ``To understand recursion you 
       echarne@uci.bitnet \\ //   \\ //  need to understand recursion.''
echarne@nrtc.northrop.com  \X/     \X/   --Andrew Koenig, 2nd Usenix C++ conf.