Hi Andreas,

> I realised that there remains an open bug to version 0.6.5. Could you
> please check whether this exists or not.

I have recently committed a patch that seems to have fixed this bug. In 
particular,
we are not linking to f2c any more because it is needed only if we also use the 
internal
BLAS, LAPACK or ARPACK implementations (which we don't use). One of my other 
patches
also ensures that dh_auto_test runs all the unit tests, and they all compile 
just fine.

FWIW, the patch I committed is temporary; the configure script in the upstream 
repo already
does a better job at deciding whether linking to f2c is needed or not, but this 
version is
likely to be included in the next release only. The patch I committed here only 
ensures that
we are not linking to f2c at all, it does not attempt to fix the detection of 
libf2c or the
logic that decides whether linking to f2c is necessary or not.

Anyway, I think that this bug can safely be closed once the updated package 
(0.7.1-2) is
uploaded. Most of the patches that I added to 0.7.1-2 now can also be removed 
once upstream
releases the next version because these patches are also merged into upstream.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org


Reply via email to