sorry, I answered only to Peter 2010/1/17 Diego Saravia <diego.saravia@xxxxxxxxx>: >> I agree it is tiresome not to get all those error messages at once, and >> therefore I always try to write my configure.ac so configure doesn't exit >> when a package is missing but just collect that information and keep on >> searching for the other packages. And then in the end (just before >> AC_OUTPUT) I print out the missing packages and exit. There is nothing in >> current Autoconf that prevents you from doing so and if you use third-party > > thats the idea, but > > AC_PROG_CC calls AC_MSG_FAILURE, I dont remember now, but I think > another AC_PROG_XXs macros call it too > > What I am doing is redefining AC_MSG_FAILURE, but Erick Blacke said > its not a good idea, I agree > > Also, I could not use AC_PROG_CC but I will need to reinvent a great > part of autoconf to do that, > > >>There is nothing in current Autoconf that prevents you from doing so and if you use third-party macros that AC_MSG_ERROR on failure, you should really ask the maintainer >>of that macro to provide a MACRO([ACTION-IF-FOUND], [ACTION->IF-NOT-FOUND]) interface. > > AC_PROG_CC is part of autoconf or is a third part macro? > > > Thank you > > -- > Diego Saravia > Diego.Saravia@xxxxxxxxx > NO FUNCIONA->dsa@xxxxxxxxxxx > -- Diego Saravia Diego.Saravia@xxxxxxxxx NO FUNCIONA->dsa@xxxxxxxxxxx _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
