On 05/21/2013 05:56 AM, Earnie Boyd wrote: > On Tue, May 21, 2013 at 7:36 AM, Ben Elliston wrote: >> >> Yes, but that requires re-running autoconf. I think we're trying to >> avoid that because if configure.in is old, you may have a lot of work >> to do to get autoreconf to work. > > So in that case, a change to the start of config.guess and config.sub > something similar to the following might be best? > > ~~~~~ > if [[ -f /usr/local/share/config/config.guess ]] > then > . /usr/local/share/config/config.guess > exit > fi > > if [[ -f /usr/share/config/config.guess ]] > then > . /usr/share/config/config.guess > exit > fi That would be fine with me, if you can get the upstream config project to agree to it, since it would not require autoconf to do anything more than recognize an environment variable. But are these scripts really source-able, or should you be directly executing them? And does it have proper avoidance of infinite loop if such a version of config.guess is installed into /usr/local/share/config/config.guess? -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf
