On Dec 9, 2013, at 3:33 PM, John Peterson <jwpeter...@gmail.com> wrote:
> On Mon, Dec 9, 2013 at 2:19 PM, Derek Gaston <fried...@gmail.com> wrote: >> So - I'm back at trying to get everything running on BG/Q (Mira) at >> Argonne... and I hit a snag where our supplied libtool is doing something >> bad - but if I just move it out of the way and set a soft-link to the system >> libtool then everything is working fine. >> >> Is there a way to tell our build system not to use our included libtool at >> all? > > Is the error during building libmesh? What is the error? I'm interested in the answer as well, but... boostrap has some simple logic in there to look for a preferred version of libtool and build ours. But at the end of the day, all bootstrap does is run $ autoreconf -iv --force so if your path is set up such that 1) autoreconf 2) automake 3) libtool point to the versions you desire, just run $ autoreconf -iv --force ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
