On Friday 07 December 2001 03:32 am, Brent Dax wrote: > I have no idea how many times this has been suggested. :^)
Well, then one more is a relatively small burden to bear. ;-) > > Seriously, the only problem I can see with it is that the modules will > have to be run in a specific order. If you can figure out a nice way to > break things up and make them run in an order we define without too much > messiness, let me know. (Just don't work *too* hard on it--this > Configure won't be like the final Configure.) Dependency-ish rules, a la make. Maybe even tied into the actual build itself. I don't think getting them to run in the right order is a problem. I think *writing* them so that they can be run in the right order is. <anecdote mode="boring"> After having spent the past several weeks trying unsuccessfully to get a "modern" open development environment on some ancient mc88100-based DGs - ancient being a relative word - I came to dread some portions of the GNU configure stuff. (And the whole experience itself.) Some minor inconsistencies, some apparant incompleteness, and just the whole level of uninformedness that ./configure gives was making the upgrade vey frustrating, and I eventually wrote it off. (After having both gawk and sed - both of which passed their tests - take over the system on a 'dirname' pattern, waiting through an hour of a binutils build to find out that 'gas' didn't want to support my configuration, and having no luck building anything other than GNU make and gcc 2.6 (and that was having worked backwards.) But all I really needed was Perl, so I thought I'd give it a gander. After all the lifeless GNU-ish configs, the Configure seemed thorough, informative, and, well, entertaining - only partly due to the seemingly random, haphazardous order it would do things in. (But in all fairness to the GNU maintainers, Perl didn't fair much better. It failed to build because of preprocessor token concatenation, it looked like, of which Configure determined it was "Ah, the good ol' days.") </anecdote> -- Bryan C. Warnock [EMAIL PROTECTED]
