On Thu, Feb 17, 2005 at 07:53:36PM +0100, olafBuddenhagen@xxxxxx wrote: > Hi, > > > > Somewhere early during ./configure, the host type is checked. If it is > > > GNU (Hurd), an ordinary build is prepared. (Checking libs, using > > > automake-generated makefile etc.) However, if it's Linux, the behaviour > > > changes completely: All the ordinary checks are skipped; instead of an > > > automake-generated makefile, a simple, hand-written makefile is used, > > > with only a couple of configuration variables substituted. > > > > Autoconf does not preclude building a `configure' that behaves as you describe, > > but it is an awkward fit. > > Sorry, not sure what you mean by "awkward fit"? Autoconf is set of macros for building shell scripts that test features of a system and adjust build files accordingly. Those macros help you perform tasks like testing for the availability of functions and headers. Nothing in Autoconf supports doing what you have described, but since you can include any shell commands you want in `configure', you could apply such logic manually, and Autoconf would more or less stay out of the way. Try it. If you have specific problems, ask. _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
