Fuck "modules" to hell for all time! Is there a way to put some "module" sanity checks at the beginning of PETSc's configure?
It seems everyone who touches a Nersc machine has module problems. We waste way to much time on "missing module" nonsense. Barry > On Oct 3, 2017, at 10:39 PM, Mark Adams <[email protected]> wrote: > > > > On Tue, Oct 3, 2017 at 4:22 PM, Satish Balay <[email protected]> wrote: > >>>>> > checking size of bool... 0./configure: line 12435: printf %s\n: command not > found > ./configure: line 12436: printf %s\n: command not found > configure: WARNING: The C++ compiler g++ cannot compile a program containing > the <string> header - this may indicate a problem with the C++ installation. > Consider configuing with --disable-cxx > configure: WARNING: Structures containing long doubles may be aligned > differently from structures with floats or longs. MPICH does not handle this > case automatically and you should avoid assumed extents for structures > containing float types. > configure: error: unable to determine matching C type for C++ bool > <<<<<< > > For some reason MPICH configure is failing. > > > balay@asterix /home/balay/petsc (maint=) > $ which printf > /usr/bin/printf > balay@asterix /home/balay/petsc (maint=) > $ rpm -qf /usr/bin/printf > coreutils-8.27-16.fc27.x86_64 > balay@asterix /home/balay/petsc (maint=) > $ > > Your machine does not have this basic coreuitls package installed? > > > We are probably missing a module, > > Satish > > On Tue, 3 Oct 2017, Dylan P. Brennan wrote: > > > > > Hello, > > > > I’m having problems configuring, any ideas? > > > > Dylan > > > > >
