Thanks.
The $PREFIX/include/makefile is just a hiccup from the installer and should
never be installed. I have fixed next and master to not copy it. In fact there
were a truckload of include/*/*/makefile that should never have been copied
over,. FIXED
Another bad copy of install stuff not mentioned is
ls ~/petscinstall/include/finclude/ftn-auto/
-tmpdir pcexotic-tmpdir
ao-tmpdir pcgasm-tmpdir
petscthreadcomm-tmpdir
dm-tmpdir pcmg-tmpdir
dmcomposite-tmpdir .... i.e. tons of work directories that should
never have been copied over. FIXED
The other complaint is $PREFIX/lib/modules/3.4.1 but in fact there are
many other things that should be complained about as well.
include/finclude -nonname-spaced directory which includes two additional
nonname-spaced sub-directories fnt-auto and fnt-custom WHAT SHOULD THIS STUFF
BE CALLED?
all subdirectories of bin get copied over including unnamed spaced maint
and julia plus lots of silly stuff gets installed that should not be installed.
I WILL FIX THIS
ls ~/petscinstall/bin/
FASTMathInstaller.py julia mpiexec.sshsync popup
uncrustify.cfg
TOPSGenerator.py maint mpiexec.uni
portabilitycheck.py update.py
adiforfix.py mapnames parseargs.py pstogif
urlget
mpiexec.gmalloc petsclogformat.py pstoxbm
urlget.py
mpiexec.lam petscmpiexec pythonscripts
win32fe
configVars.py mpiexec.llrun petscnagupgrade.py saws
mpiexec.poe petscnagupgrade.pyc taucc.py
mpiexec.prun petscrun
The famous conf directory gets copied over
> On Dec 30, 2014, at 4:00 PM, Aron Ahmadia <[email protected]> wrote:
>
>
> On Tue, Dec 30, 2014 at 4:54 PM, Barry Smith <[email protected]> wrote:
>
> Tell us what we need to fix.
>
> The issues were brought up in:
> http://lists.mcs.anl.gov/pipermail/petsc-dev/2013-October/013420.html
Hi All,
The PR has raised a few issues in what PETSc does when it performs a
prefix install. In particular, PETSc generates the following files:
$PREFIX/include/makefile
$PREFIX/lib/modules/3.4.1
Neither of these have been properly namespaced. I'd suggest changing these to:
$PREFIX/include/petsc/makefile
$PREFIX/lib/modules/petsc/3.4.1
I'm not sure about the latter, I really don't know how package
managers deal with local modules install, or if it's worth even
putting it in if the user is requesting a PREFIX install.
Another option would be to include the PETSc ARCH in the directory namespacing:
$PREFIX/include/petsc/linux-gnu/makefile
$PREFIX/lib/modules/petsc/linux-gnu/3.4.1
Thoughts?
-A
>
> I don't know how you track these issues internally, but it didn't seem to be
> resolved when I looked at the mailing list.
>
> A
