> > Hi! > > I just noticed, that when i enable a config.cache that is used by more > than one package is problematic, when the first on checks for the build > system type only, and the second for both build and host system type. > This is, because the host system type check uses ac_cv_build_alias, > which is set only if build system type (ac_cv_build) is not cached. > > Now the first package caches the build system type, but not the host > system type, and the second package cannot configure, since the call to > config.sub misses an argument (since ac_cv_build_alias is used, which > is > empty, since build system type was cached)... Another cache problem is with updating the cache file. This seems rather unsafe for parallel builds using the same cache file. What about not using cat for updating, but writing into a separate file, and moving it over the original file (and not checking the mv return code). This way the worst that can happen, is that cache values are lost if two configure scripts try to update simultaneously - which shouldn't be too critical, since they are simply checked again the next time.... Thoughts? Cheers, Markus > > Hope I made myself clear :) excuse my English... > > Cheers, Markus > > > _______________________________________________ > Autoconf mailing list > Autoconf@xxxxxxx > http://lists.gnu.org/mailman/listinfo/autoconf _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
