On Wed, May 26, 2010 at 11:04 AM, Mladen Jurak <[email protected]> wrote: > On 26.05.2010 17:54, John Peterson wrote: >> On Wed, May 26, 2010 at 10:52 AM, Mladen Jurak<[email protected]> wrote: >> >>> Running bootstrap didn't help. >>> >>> The problem is that configure file takes the first existing shell >>> from the sequence "sh bash ksh sh5", so it usually takes sh. On my >>> system (Debian/squeeze) sh=dash and this is an inadequate choice. I solved >>> it by changing the order of the shell sequence to "bash ksh sh5 sh". >>> >> Very interesting! So is the dash shell (I've never heard of it) not >> sh-compatible, or is our configure script generating a bash-specific >> script? >> >> > Dash is something new for me too. The man page says: > > dash is the standard command interpreter for the system. > The current version of dash is in the process of being changed to conform > with the POSIX 1003.2 and 1003.2a specifications for the shell. This > version
Hrm... sounds like it might not be 100% perfect yet but 1003.2 -> 1003.2a seems like it should be a pretty small change?! In any case, I'm glad you were able to find the workaround, hopefully this thread will pop up for anyone searching about this issue in the future... -- John ------------------------------------------------------------------------------ _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
