[Bug 489686] Review Request: armadillo - fast C++ matrix library with interfaces to LAPACK and ATLAS

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=489686





--- Comment #52 from Jussi Lehtola <jussi.lehtola at iki.fi>  2009-06-14 02:24:34 EDT ---
(In reply to comment #51)
> (In reply to comment #50)
> > ...
> > But, as lapack-devel and blas-devel include only libraries 
> > (and not header files), I would exclude the correspondent 
> > dependency from the 'Requires:' part.
> 
> I see what you're getting at, but I'm not totally clear on this. Users will be
> linking their armadillo programs with -larmadillo, which in turn should
> automatically pull in the lapack and blas libraries.  However, aren't
> "/usr/lib/liblapack.so" and "/usr/lib/libblas.so" required for this to work? 
> (they're present in lapack-devel and blas-devel).

The armadillo library is linked against blas and lapack, this is picked up by
rpm which adds dependencies on the soname'd libraries as Denis said in #48. One
doesn't need blas-devel and lapack-devel to use armadillo, just blas and lapack
which are automatically pulled in.

> > The same way, I would exclude dependency on 'libstdc++-devel'.
> 
> Armadillo explicitly needs the header files from "libstdc++-devel", unless we
> can assume that a c++ compiler will always be installed ?  (I didn't want to
> make a dependency on gcc-c++, as people may possibly want to use another
> compiler).

This, on the other hand I'd keep, since nothing picks this up automatically.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.