🚀 go-pugleaf

In article <2ACF5C7B.4874@news.service.uci.edu> steve@fisher.bio.uci.edu  
(Steve Frank) writes:
> 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)


> 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.  

No, no. The problem is not gcc, but the location of the include files. A  
lot of scripts will search /usr/include/*.h for several defines of  
constants, functions and other stuff, but the whole include directory has  
been reorganized, so for example /usr/include/stdio.h is moved to  
/usr/include/ansi/stdio.h and the normal configure scripts will not search  
in those directories.

The result is, that simple programs, that compiled under 2.1, will not  
compile without errors.

What a shame..

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