1) Try to build the parts that are least likely to build correctly, last
Parts for which the pre-requisites are not found, are not built (or at least, should not be attempted).
2) Give an informative message about how to disable the build of problematic portions, upon getting an error related to them
This happens at prerequisite-detection time.
"Searching for foo: not found"
And building something that requires 'foo' is disabled (in most cases, modulo any bugs that prevent that disablement).
3) Have autoconf see if it can find the prerequisites for building problematic parts, and if it cannot, then don't attempt it
This is what autoconf does, when designed correctly.
Incidentally, someone from *nac.uci.edu has been pounding the plkr.org domain with far too many repeated hits with their Plucker spider over and over and over. They have been blocked.
Once the error in their script has been corrected, I will remove the block.
David A. Desrosiers [EMAIL PROTECTED] http://gnu-designs.com
_______________________________________________ plucker-list mailing list [email protected] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
