On Nov 1, 2013, at 11:35 PM, "John Peterson" <jwpeter...@gmail.com> wrote:
> Why on earth would IBM do this? It differs from literally every other > compiler that I've ever seen. I don't know if there's a built-in autoconf > test for "how to #define stuff on the compile line" but that seems like > that's what we'd need here to fix this the right way. Oh man, I haven't used these compilers since the days of the power3 at TACC. One possibility - is there a native autotools installation on that machine, and if so perhaps try running 'autoreconf -iv --force' directly, then reconfiguring? Sometimes exotic quirks like this are fixed on proprietary machines but those changes are not pushed upstream, so if there is a vendor-provided autotools it may at least do the preprocessor properly! -Ben ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
