On 2013-10-10 09:38, Roland Kaufmann wrote:
suitesparse is in EPEL. If the IT department has problems
installing it on a computation cluster, then IMO that's a problem
on its own.
On 2013-10-10 10:06, Alf Birger Rustad wrote:
Then you do not understand corporate IT. EPEL is not supported by Red
Hat. Hence you are basically asking why should anybody pay for Red
Hat support. After all, we could just install Arch and take the
support burden and risk ourselves.
No, that is not the same. If you install Arch, you choose a
non-supported distro where a supported alternative exist; that is not
the case with suitesparse.
I understand why they don't want to install it: to keep their own list
of things to keep track of small. And by itself that is a perfectly
rational goal. But it is a sub-optimalization: The very small gain they
have is outweighted by your much greater cost.
If I were a system administrator I would much rather have people using
EPEL libraries than compiling their own, because those are less likely
to break during upgrades.
>> If you pass -Dumfpack_LIBRARY=/foo/UMFPACK/Lib/libumfpack.a I think
>> it should work
That will make our build script slightly more involved, but should
work. It will however not work for the next user who wants to kick
the tires of OPM (in the sense that the binaries will fail by default
until the user figures out a solution like this one).
Which really means that we should add a check in the buildsystem which
fails if MPI_FOUND is defined but SUITESPARSE_FOUND is not.
--
Roland.
_______________________________________________
Opm mailing list
[email protected]
http://www.opm-project.org/mailman/listinfo/opm
