🚀 go-pugleaf

In article <31@ftms.UUCP> brown@ftms.UUCP (Vidiot) writes:
>Why doesn't GNU software use the Configure idea of configuring GNU packages?
>Software like rn and elm use it, making for a system that knows what it has,
>doesn't have and therefore knows what it can or can't do.

Configure does a terrible job --- it makes little or no allowances for
cross compilation, hybrid environments, or alternate compilers.

When I had my '386, I spent a lot of time bringing the system header
files into conformance with ANSI, POSIX, X/Open, etc. and put them in
/usr/gnu/lib/gcc-include/*.  The end result was a very slick development
environment.

But when I have to compile elm, rn, or perl, I find that Configure doesn't
ask me which directory include files were stored, it just blindly gropes
around /usr/include/*.  

To be useful, Configure would have ask for confirmation after it
each "guess" it makes about the system.  Since that basically means 
steping through lots of questions, I'd rather edit config.h and
forget the whole Configure mess.

    --jtc

-- 
J.T. Conklin    jtc@motcad.portal.com, ...!portal!motcad!jtc