<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">Hypre problem resolved. PETSc commit 05f86fb made in August 05, 2019 added the line 'self.installwithbatch = 0' to the __init__ method of the Configure class in the file petsc/config/BuildSystem/config/packages/hypre.py to fix a bug with hypre installation on Cray KNL systems. Since the machine I was installing os was an SGI system, I decided to try switching to 'self.installwithbatch = 1' and it worked! The configure script was finally able to run to completion.</div><div dir="ltr"><br></div><div>Perhaps there can be a Cray flag for configure that can control this, since it is only Cray's that have this problem with Hypre?</div><div><br></div><div>For my benefit when I have to do this again - </div><div>To get moose/petsc/scripts/update_and_rebuild_petsc.sh to run on an SGI system as a batch job, I had to:</div><div><br></div><div>Make sure the git (gnu version) module was loaded</div><div>git clone moose</div><div>cd to the petsc directory and git clone the petsc submodule, but make sure to pull the latest commit. The commit that the moose repo refers to is outdated.</div><div>cd back to the moose directory, git add petsc and git commit so that the newest petsc commit gets used by the update script. otherwise the old commit will be used.</div><div>download the tarballs for fblaspack, hypre, metis, mumps, parmetis, scalapack, (PT)scotch, slepc, and superLU_dist. The URLS are in the __init__ methods of the relevant files inmost/petsc/config/BuildSystem/config/packages/</div><div>alter moose/scripts/update_and_rebuild_petsc.sh script so that it is a working PBS batch job. Be sure to module swap to the gcc compiler and module load git (gnu version) and alter the ./configure command arguments</div><div> adding</div><div> --with-cudac=0</div><div> --with-batch=1</div><div> changing</div><div> --download-<package>=/path/to/thirdparty/package/tarball</div><div>If the supercomputer is <b>not</b> a Cray KNL system, change line 26 of moose/petsc/config/BuildSystem/config/packages/hypre.py from 'self.installwithbath = 0' to 'self.installwithbatch = 1', otherwise, install hypre on its own and use --with-hypre-dir=/path/to/hypre in the ./configure command</div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jan 31, 2020 at 10:06 AM Tomas Mondragon <<a href="mailto:tom.alex.mondragon@gmail.com">tom.alex.mondragon@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr">Thanks for the change to base.py. Pulling the commit, confirm was able to skip over lgrind and c2html. I did have a problem with Parmetis, but that was because I was using an old ParMetis commit accidentally. Fixed by downloading the right commit of ParMetis.<div><br></div><div>My current problem is with Hypre. Apparently --download-hypre cannot be used with --with-batch=1 even if the download URL is on the local machine. The configuration.log that resulted is attached for anyone who may be interested.</div></div>
<p></p>
-- <br>
You received this message because you are subscribed to a topic in the Google Groups "moose-users" group.<br>
To unsubscribe from this topic, visit <a href="https://groups.google.com/d/topic/moose-users/2xZsBpG-DtY/unsubscribe" target="_blank">https://groups.google.com/d/topic/moose-users/2xZsBpG-DtY/unsubscribe</a>.<br>
To unsubscribe from this group and all its topics, send an email to <a href="mailto:moose-users+unsubscribe@googlegroups.com" target="_blank">moose-users+unsubscribe@googlegroups.com</a>.<br>
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/moose-users/a34fa09e-a4f5-4225-8933-34eb36759260%40googlegroups.com?utm_medium=email&utm_source=footer" target="_blank">https://groups.google.com/d/msgid/moose-users/a34fa09e-a4f5-4225-8933-34eb36759260%40googlegroups.com</a>.<br>
</blockquote></div></div>