But this is a different failure. I am/was able to get p4est to work by
rerunning configure. Is this failure cause by p4est. NERSC changed a lot of
stuff on Edison, that is why I am rebuilding for someone.

On Thu, Aug 10, 2017 at 10:34 AM, Tobin Isaac <tis...@cc.gatech.edu> wrote:

>
> This seems to be a recurring theme.  p4est code is quite stable at the
> moment.  Even though we have `--download-p4est`, it might be a better
> idea to install p4est once externally to petsc and use `--with-p4est`,
> especially when getting autotools are a sticking point.
>
>   Toby
>
> On Thu, Aug 10, 2017 at 10:27:58AM +0900, Mark Adams wrote:
> > Yea, I saw that. I'll ask NERSC. As I recall the auto stuff was for
> p4est.
> > It seems to die before that.
> >
> > On Thu, Aug 10, 2017 at 10:21 AM, Matthew Knepley <knep...@gmail.com>
> wrote:
> >
> > > On Wed, Aug 9, 2017 at 7:42 PM, Mark Adams <mfad...@lbl.gov> wrote:
> > >
> > >> NERSC changed some stuff and my configure is crashing. Any ideas?
> > >>
> > >
> > > It sure looks like you have a module problem:
> > >
> > > Executing: cc -c -o /tmp/petsc-BbxLhU/config.setCompilers/conftest.o
> > > -I/tmp/petsc-BbxLhU/config.setCompilers   /tmp/petsc-BbxLhU/config.
> > > setCompilers/conftest.c
> > > Possible ERROR while running compiler:
> > > stderr:
> > > ModuleCmd_Load.c(244):ERROR:105: Unable to locate a modulefile for
> > > 'autoconf'
> > > ModuleCmd_Load.c(244):ERROR:105: Unable to locate a modulefile for
> > > 'automake'
> > > ModuleCmd_Load.c(244):ERROR:105: Unable to locate a modulefile for
> > > 'valgrind'
> > >
> > >
> > >    Matt
> > >
> > >
> > >> Thanks
> > >>
> > >
> > >
> > >
> > > --
> > > What most experimenters take for granted before they begin their
> > > experiments is infinitely more interesting than any results to which
> their
> > > experiments lead.
> > > -- Norbert Wiener
> > >
> > > http://www.caam.rice.edu/~mk51/
> > >
>

Reply via email to