On Feb 6, 2013, at 1:35 PM, Roy Stogner <royst...@ices.utexas.edu> wrote:
> I can't yet actually find anything wrong in our autotools scripts that > would be causing this, but I can't believe that the bug is in autoconf > itself... that whole system relies on shell scripting so paranoid that > it eschews every little non-POSIXism in bash, surely they can't have > made the most classic of script-newb mistakes? No, that would be my newb mistake. c.f. configure.ac: # hackery. If we are supporting nested autoconf packages and we want to specify # additional arguments to be passed to those packages, do that here. # Specifically, we append libmesh_subpackage_arguments to ac_configure_args # before AC_OUTPUT recurses into our subpackages if (test "x$enablenested" = "xyes"); then ac_configure_args_SAVE="$ac_configure_args" ac_configure_args="$ac_configure_args $libmesh_subpackage_arguments CXX=$CXX CC=$CC F77=$F77 FC=$FC" fi # Create output files. Also configures any sub packages AC_OUTPUT What I am trying to accomplish is to force netcdf to use our compilers. Without this it''l happily go and find its own, regardless of what we are using. note that this is not strictly a problem but seems silly to me. Can you try quoting the CXX=$CXX and see if that fixes you? -Ben ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
