Re: Removing ATLAS?
Hi Sébastian,
Am Sat, Jul 08, 2023 at 10:01:15AM +0200 schrieb Sébastien Villemot:
>
> So, given all that, I’m inclined to (try to) remove atlas during the
> trixie development cycle.
Sounds reasonable.
> Any thought on this?
I've checked my responsibility for the dependencies and stumbled about
emmax
emmax.c:10:10: fatal error: clapack.h: No such file or directory
10 | #include <clapack.h>
| ^~~~~~~~~~~
compilation terminated.
and noticed
$ apt-file search clapack.h
libatlas-base-dev: /usr/include/x86_64-linux-gnu/clapack.h
... (other instances are not blas related)
which was probably the reason why I've picked libatlas-base-dev
originally. I would not say that emmax is important and its
also a not maintained upstream any more. However, I vaguely
remember that this
#include <clapack.h>
in some code pieces of Debian Med was the reason to actually
pick this blas implementation. Any hint how to deal with such
cases?
Kind regards
Andreas.
> Checking reverse dependencies...
> # Broken Depends:
> ceres-solver: libceres-dev
> libceres3
> colmap: colmap [amd64 arm64 i386 mips64el mipsel ppc64el s390x]
> dune-common: libdune-common-dev
> emmax: emmax
> ergo: ergo
> iml: libiml0
> nipy: python3-nipy-lib [armel mipsel]
> psfex: psfex
> python-escript: python3-escript [armel mipsel]
> python3-escript-mpi [armel mipsel]
> qm-dsp: libqm-dsp0
> scamp: scamp [amd64 arm64 mips64el ppc64el s390x]
> scikit-misc: python3-skmisc
> sight: libsight [amd64]
> source-extractor: source-extractor
> xmds2: xmds2
>
> # Broken Build-Depends:
> ceres-solver: libatlas-base-dev
> dune-common: libatlas-base-dev
> emmax: libatlas-base-dev
> libatlas3-base
> ergo: libatlas-base-dev
> ghmm: libatlas-base-dev
> halide: libatlas-base-dev
> hpcc: libatlas-base-dev
> iml: libatlas-base-dev
> ncl: libatlas3-base
> odin: libatlas-base-dev
> opm-material: libatlas-base-dev
> phast: libatlas-base-dev
> plink1.9: libatlas-base-dev
> plink2: libatlas-base-dev
> psfex: libatlas-base-dev
> qm-dsp: libatlas-base-dev
> scamp: libatlas-base-dev
> scikit-misc: libatlas-base-dev
> source-extractor: libatlas-base-dev
> theli: libatlas-base-dev
> xmds2: libatlas-base-dev
>
> Dependency problem found.
>
--
http://fam-tille.de
Reply to: