Peter Boyle wrote: > Mine is one of a class of apps that regularly use autoconf > in parallel computer codes. These by nature are often cross > tools, and frequently use vendor supplied wrappers like "mpicxx" as "CXX" > etc to sort out the libraries & compile environment... I recommend you create symlinks (for example) from cpu-vendor-os-mpicxx (or whatever) to mpicxx so that the auto tools find your cross tools where they are expecting to find them. This is, IME, a much easier and better solution, especially if one implements it using something like http://modules.sf.net, where one may need to maintain different versions of the stock tools on the build machine in order to use particular versions of those tools for any given product release build. H _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
