> Apparently we aren't really set up for this branch of the > if-statement, because we don't have a dist_version file (unless 'svn > export' automatically creates that?). > > So it could probably be fixed with an > > if [ -f $file ]; then ... fi > > type check. > > Note also that an empty string eventually gets substituted for > LIBMESH_BUILD_VERSION in libmesh_config.h > > #define LIBMESH_BUILD_VERSION "" > > Is that OK behavior going forward? What if anything is > LIBMESH_BUILD_VERSION supposed to be used for?
Awesome - I'll see about recreating this and fixing it. ATM nothing is done with this, but the idea is include it in perhaps libmesh_error() or other macros to help create more reproducible bug reports. For example, on my machine this reads #define LIBMESH_BUILD_VERSION "6449M" which makes sense: benkirk(4)$ svn info Path: . URL: https://libmesh.svn.sourceforge.net/svnroot/libmesh/trunk/libmesh Repository Root: https://libmesh.svn.sourceforge.net/svnroot/libmesh Repository UUID: 434f946d-2f3d-0410-ba4c-cb9f52fb0dbf Revision: 6449 Node Kind: directory Schedule: normal Last Changed Author: benkirk Last Changed Rev: 6442 Last Changed Date: 2012-11-24 10:27:52 -0600 (Sat, 24 Nov 2012) benkirk(5)$ svn status M configure ? contrib/autotools/automake-1.12.5.tar.gz ? examples/foo.sh ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
