This may be a stupid question but is there a good way to run autoconf in a chrooted environment? From what I can tell the AS_UNAME function calls uname which gets information about the base kernel that is installed and not the kernel that is installed in the chrooted environment. Is there a function that does the same thing as AS_UNAME without actually using uname or is this something that has yet to be developed. It would be very helpful to have such functionality for building packages on build machines which are running different kernels than what is being run where you want to install the package. The specific case where I am encountering this is building lustre with SUSE's open build service. Thanks -Peter _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf
