On Sep 17, 2012, at 9:05 AM, Roy Stogner <[email protected]> wrote:
> > Silly hunch: could you try rerunning things after exporting > CONFIG_SHELL=/bin/bash and/or CONFIG_SHELL=/bin/sh ? > > I thought libMesh was immune to this error now, but I've seen other > autotools packages have similar-looking problems when running on > systems where bash was the full-kitchen-sink-GNU-bash and sh was a > stripped-down POSIX-only Bourne shell. > --- > Roy After exporting those two variables, running the command below still fails and gives the same error. ./configure CC=/usr/local/gfortran/bin/gcc CXX=/usr/local/gfortran/bin/g++ FC=gfortran F77=gfortran PETSC_DIR=$HOME/sfw/petsc/3.2-p6 PETSC_ARCH=$HOME/sfw/petsc/3.2-p6/darwin --enable-petsc --enable-mpi --prefix=$HOME/sfw/libmesh \ ------------------------------------------------------------------------------ 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-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
