🚀 go-pugleaf

In article <RICH.92May13100840@cygnus.cygnus.com>, rich@cygnus.cygnus.com (K. Richard Pixley) writes:
> 
> With integrated Makefiles, I can build and three stage across all
> tools in a matter of hours, (ok, days on a sun3), and the entire
> exercise boils down to:
> 
> 	configure ...
> 	make all install

Yes, on a Sun. But, for example,

 -- if you don't use gcc (because debugging on certain machines does
    not work...)
 -- if an alloca() exists on your system but is broken

then you go back, change all created Makefiles (after all, your
friendly package author added an alloca source...) and make it again.
Other examples exist, I just remember this case.

The problem is: if configure finds something it will use it. And if I
know it better, that this `thing' should not be used, I will have no
chance in just saying `configure'...

I.e.: IMNSHO GNU configure needs urgently a hints file to be of real
use. Something like <machine>.cf/site.def in the X11 Imakefiles or
like the hints files of Larry Wall's Configure. A place where you can
tell configure about

 -- weaknesses of your systems (stuff which exists but shall be ignored)
 -- your wishes about configurations (eg, I don't want to have stuff
    in /usr/gnu)
 -- add locations, where configure should look in addition.

The possibility to specify the above configuration on the command
line is not enough: I want to specify it once, set an environment
variable where this hints file is, and be able to forget it
afterwards. It's important to note that I don't want application
specific infos in this hint file; it's more something of an overall
local configuration of the GNU project at my site.

--
Joachim

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Joachim Schrod			Email: schrod@iti.informatik.th-darmstadt.de
Computer Science Department
Technical University of Darmstadt, Germany