Re: GNOME and Sun Workshop 4.2 compiler

[allbery ece cmu edu]

On 27 Oct, Raja R Harinath wrote:
| Miguel de Icaza <miguel@nuclecu.unam.mx> writes:
| > > I used to do that, along with Purify.  But to build from CVS you
| > > *must* use gcc:  in non-"release" code libtool does stuff that only
| > > works with gcc.
| > 
| > This seems terrible.  How can we fix this?
| 
| It's probably not libtool, but automake -- the automake automatic
| dependency system depends on gcc.  One option is to build first with
+--->8

automake is also part of it.  But I recall libtool doing strange
things as well (possibly in response to the automake magic in the
compile lines).

Also, libtool + Purify failed because libtool's handling of shared
library dependencies effectively overrode the use of Purify-processed
shared libraries, resulting in a runtime error when running the
Purify'd program.  I ended up copying the Purify-postprocessed
libraries (typically in a tree under /tmp or /var/tmp) over the
unprocessed libraries in e.g. /opt/gnome, thus requiring that anyone
running the binaries had to deal with Purify.

-- 
brandon s. allbery	[os/2][linux][solaris][japh]	 allbery@kf8nh.apk.net
system administrator	     [WAY too many hats]	   allbery@ece.cmu.edu
electrical and computer engineering					 KF8NH
carnegie mellon university	  ["better check the oblivious first" -ke6sls]