On Sun, 25 Mar 2012, Jed Brown wrote:
On Sun, Mar 25, 2012 at 13:47, Satish Balay <[email protected]> wrote:
The default organization for --with-package-dir should be the default organization used by the package - not what petsc configure dictates whats suitable for itself. For ex: look at MKL - and the wierd path scheems it has developed over the past many versions. We support most of them.
The cusp installation instructions _say_ to put it in /some/path/include. That is reasonable, considering that the package consists of headers. Of course the user could choose to put it somewhere else, but they can inflict that hardship on themselves using --includedir=.
They give 2 options . [one /usr/local/cuda/include, the other /home/nathan/cuda_libraries/cusp] For your consistancy [wrt to santity of prefix definition] you say - petsc configure should support 1 wirh packaage-dir - and users who choose 2 should use --with-package-includ option. I don't agree with this logic.
I don't see how the fact that cusp does not provide an install target implies that --with-cusp-dir=$prefix has some meaning different from "prefix" with other packages.
We don't really insist on --with-package-dir=prefix. So far we've been accomodating varations of 'package installs' that we could reasonably support.
I don't care that MKL has a funny layout, there is still a reasonably well-defined concept of what the prefix is.
But based on the your previous statement - we should not support mkl organiztion with --package-dir option [as it doesn't comply with prefix organizaton], insist users should always --with-package-lib option. Satish