[petsc-dev] buildsystem: cusp location

Jed Brown jedbrown at mcs.anl.gov
Sun Mar 25 13:56:27 CDT 2012


On Sun, Mar 25, 2012 at 13:47, Satish Balay <balay at mcs.anl.gov> 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=.

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.

I don't care that MKL has a funny layout, there is still a reasonably
well-defined concept of what the prefix is.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120325/a9bd195b/attachment.html>


More information about the petsc-dev mailing list