🚀 go-pugleaf

In article <BvLpMs.zy@dannug.dk> karthy@dannug.dk (Karsten Thygesen)  
writes:
> 
> Anyone knows if GNU is planning to change their autoconf system to  
support  
> NeXT's new "smart" architecture? There is a LOT of programs which is  
> difficult to compile under 3.0 because of this. (like Taylor UUCP, perl  
> and more)
> 
> Why did they do it?? Before is was a (more or less) clean BSD machine  
> (from a Unix point of view), but know it's a...Well..A NeXT..
> 
> Karsten.
> 

The following may solve some problems with compiling GNU tools under 3.0.   
I have made these observations while compiling GNU find and diff.  I have  
not tried perl, which may be more difficult.

It appears that GNU's configure script first checks to see if gcc is  
installed.  If you have installed gcc (2.1 or 2.2.2, for example), then  
the configure script assumes you will use gcc to compile the program.  It  
then checks for location of include files among other things.  The  
defaults created will not work (at least if your gcc version was compiled  
under NeXT OS 2.1).  If you simply go into the Makefile and change gcc to  
cc, this will not work either.  

I decided to delete my old version of gcc.  I then ran the configure  
script and compiled without a problem.  I would guess that if you simply  
"hid" gcc from the configure script, all would be well ("mv  
/usr/local/bin/gcc /usr/local/bin/hide.gcc"), but I have not tested this.

> 
> -- 
> Karsten Thygesen (karthy@dannug.dk) (NeXT-Mail welcome)
> Danish NeXT Users Group
> Phone: +45 98 12 42 59
> Aalborg, Denmark.

--
----------------------------------------------------------
Steven Frank        	| Tel: 714-725-2244
Dept. of Ecology and 	| Fax: 714-725-2181
  Evolutionary Biology	| email: safrank@uci.edu
Univ. of California   	| bitnt: safrank@uci.bitnet
Irvine, CA 92717      	|