<br>So the below actually occurs with petsc-3.1, but I believe not much has changed in petsc-dev.<br><br>This is a config crash, which I guess is my own fault, so that's not the real issue:<br><br><blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote">
TESTING: configureDefaultArch from PETSc.Configure(config/PETSc/Configure.py:461)<br>*******************************************************************************<br> CONFIGURATION CRASH (Please send configure.log to <a href="mailto:petsc-maint@mcs.anl.gov">petsc-maint@mcs.anl.gov</a>)<br>
*******************************************************************************<br>[Errno 13] Permission denied: 'conf/petscvariables' File "./config/configure.py", line 250, in petsc_configure<br> framework.configure(out = sys.stdout)<br>
File "/home/kai/src/petsc-3.1/config/BuildSystem/config/framework.py", line 930, in configure<br> child.configure()<br> File "/home/kai/src/petsc-3.1/config/PETSc/Configure.py", line 562, in configure<br>
self.executeTest(self.configureDefaultArch)<br> File "/home/kai/src/petsc-3.1/config/BuildSystem/config/base.py", line 97, in executeTest<br> ret = apply(test, args,kargs)<br> File "/home/kai/src/petsc-3.1/config/PETSc/Configure.py", line 464, in configureDefaultArch<br>
fd = file(conffile, 'w')<br></blockquote><br>The reason for the "permission denied" is that I cannot easily install a petsc that I built as a user, as I normally do with all kinds of other software. If I do "sudo make install", it fails with "mpicc not found" (actually, it doesn't fail, it says install complete, but the install then doesn't work). I can work around that by making sure I put the right mpicc into my path as root before I "make install", but it's not as convenient as it could be. autoconf/automake software normally builds libraries as user that can be directly installed without having to be relinked, so I know it's possible to make do without relinking (unless using --disable-fast-install). Another side effect is that apparently I ended up with files owned by root in my home directory, which gave the problem above later.<br>
<br>A second, not really related issue:<br><br>In my application's build, I use "make getincludedirs / getlinklibs" to figure out how to build with / link with petsc, I suppose this is how it should be done? Unfortunately it doesn't work so well with an installed version of petsc, since the makefile doesn't get installed with the rest of things. Should the makefile get installed, or should I be using another way of figuring out this info?<br>
<br>--Kai<br><br><br><br clear="all"><br>-- <br>Kai Germaschewski<br>Assistant Professor, Dept of Physics / Space Science Center<br>University of New Hampshire, Durham, NH 03824<br>office: Morse Hall 245E<br>phone: +1-603-862-2912<br>
fax: +1-603-862-2771<br><br>