* Dr. David Kirkby wrote on Fri, Oct 16, 2009 at 12:15:19PM CEST: > Ralf Wildenhues wrote: > >In any case, you should not use $foobar for both; if you need both, have > >two variables, which can default to the same thing. And let your user > >know which is what, and how they can be overridden. > > > >>AC_CHECK_PROG(foobar,bash,[yes],[no],[]) > >>if test x$foobar != xyes > > > >The foobar variable will not be set to "yes" if bash is found anywhere, > >but to the command you can use to invoke bash. > > Strange that, as it seemed to work. If I understand you correctly, > (which I guess I am not), you are implying the script will not work > at all. You are right. I simply totally forgot to look past AC_CHECK_PROG(foobar,bash > I already had one of AC_CANONICAL_BUILD or AC_CANONICAL_BUILD, but > now have both. How can I use them? case $host in *-*-solaris*) ... ;; *-*-hpux*) ... ;; esac or case $host_os in solaris*) ... ;; hpux*) ... ;; esac > I do not want to test for each individual release of HP-UX before > giving a message. There must be hundreds of minor releases, and I've > no idea what they are. So just test for the inital part of the OS name as above. HTH. Cheers, Ralf _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
