It looks like the libMesh configure ends up running the netcdf v4 configure, passing our relevant options and environment variables to it... but *without* properly escaping any spaces first, so that 'CC="distcc gcc"' becomes '"CC=distcc" gcc'.
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? --- Roy ------------------------------------------------------------------------------ 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
