No problem here, and congratulations dad!! -Ben
On Jun 1, 2012, at 10:08 PM, "Roy Stogner" <royst...@ices.utexas.edu> wrote: > > I'd like to switch libMesh over to use the latter (posted at > http://users.ices.utexas.edu/~roystgnr/boost.m4 for collaborators > without PECOS svn access), or at least modify the former to test some > environment variables before falling back on the system paths. Our > current ax_boost stuff doesn't autodetect BOOST_ROOT, BOOST_DIR, or > BOOST_INCLUDE, and when it does end up finding boost headers in > /usr/include, the resulting -I/usr/include on some of my machines can > end up trashing other packages (the upgraded Parmetis, but vtk and > other popular stuff is similarly vulnerable) where a /usr prefixed > install of an obsolete version conflicts with our module install. > > I'm getting started on this myself (by adding env variable tests to > our version, as the path-of-least-resistance which doesn't require > modifying configure.in on trunk or configure.ac on branch) but if > anyone prefers a different solution feel free to speak up. > > Also: Roy 3.0 is here: a 3.75 kg boy currently sleep cycling every 2 > hours. If anyone else wants to implement that "create a new branch > for insufficiently tests changes" idea, now would be a good time. If > not, I'd suggest being paranoid before building anything critical > against whatever sleep-deprived commits I shove in trunk for the next > couple months. > --- > Roy ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
