> On 2/20/12 4:41 PM, Kirk, Benjamin (JSC-EG311) wrote: >> Plus, moving to a proper libtool installation will help in the future with >> shared libraries on multiple platforms (yeah, looking at you OSX). > > Several years ago, I spent a lot of time trying to get > libtool+autoconf+automake to work on the Cray XT4 at PSC. I ultimately > had to give up on libtool --- it was taking too much time to figure out > how to rig it to work. Just autoconf+automake seemed to work fine on > that system, however. > > Hopefully things are better now, but it might be a good idea to verify > that libtool works on whatever "exotic" systems you have access to > before going all in...
Thanks for the heads up. I googled the symptoms you describe and it seems that on the XT4 you link with different libraries based on the type of node you were on... and maybe libtool was snarfing the compile line on one machine and executing it on another where some libraries were different. In any case - it is nice to be aware of that issue. I believe we could easily fall back to a no-libtool build option in that case, at the expense of only getting static libs on that platform. We had a similar issue ages ago on the power 4 (or was it 3??) that forced us to use static libraries. -Ben ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
