[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 #48 from Denis Arnaud <denis.arnaud_fedora at m4x.org>  2009-06-13 16:11:03 EDT ---
(In reply to comment #47)
> 
> Unusual. Typically, explicit Requires for a -devel package are added because
> building with the -devel package requires files contained within additional
> -devel packages (e.g. headers which are included by default). At least the
> Boost headers are included by the files in armadillo-devel -- and there is no
> pkg-config file and therefore no automatic dependency-chain based on the
> Requires found in the pkg-config file.  

With the version without the 'Requires:' line, after installation of the RPMs,
I get:
# rpm -qpR armadillo-0.6.11-8.fc10.x86_64.rpm 
[...]
libblas.so.3()(64bit)  
libc.so.6(GLIBC_2.2.5)(64bit)  
libcblas.so.3()(64bit)  
libgcc_s.so.1()(64bit)  
liblapack.so.3()(64bit)  
liblapack_atlas.so.3()(64bit)  
libstdc++.so.6(GLIBCXX_3.4)(64bit)  

# ldd -r /usr/lib64/libarmadillo.so.0.6.11 
[...]
liblapack_atlas.so.3 => /usr/lib64/atlas/liblapack_atlas.so.3
(0x00007fd825c3a000)
libcblas.so.3 => /usr/lib64/atlas/libcblas.so.3 (0x00007fd825a1c000)
libblas.so.3 => /usr/lib64/atlas/libblas.so.3 (0x00007fd825067000)
liblapack.so.3 => /usr/lib64/atlas/liblapack.so.3 (0x00007fd8248ab000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007fd8245a0000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fd824104000)
libc.so.6 => /lib64/libc.so.6 (0x00007fd823d91000)
libf77blas.so.3 => /usr/lib64/atlas/libf77blas.so.3 (0x00007fd823b74000)
libatlas.so.3 => /usr/lib64/atlas/libatlas.so.3 (0x00007fd8231f4000)
libgfortran.so.3 => /usr/lib64/libgfortran.so.3 (0x00007fd822f19000)

Indeed, the Boost libraries are not needed, apparently because the
ARMA_USE_BOOST environment variable is not set to true when calling cmake. That
way, Armadillo does not use Boost, even when it is present on the building
platform. In the header files delivered with the -devel sub-package, Boost is
not used as, but through a specific wrapper, namely arma_boost, which does not
need Boost when the ARMA_USE_BOOST variable is set to false.

We may try to alter the specification file, so as to define the ARMA_USE_BOOST
variable to true. In that case, the RPM building process should detect the
dependency on Boost, I guess.

Or did I miss something?

-- 
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.