Bug#923607: openblas: FTBFS if CPU is not detected

[Sébastien Villemot]

Dear Santiago,

Le samedi 02 mars 2019 à 18:11 +0000, Santiago Vila a écrit :
> Package: src:openblas
> Version: 0.3.5+ds-2
> Severity: serious
> Tags: ftbfs
> 
> I tried to build this package in buster but it failed:

[…]
> make[2]: *** [Makefile.prebuild:66: getarch_2nd] Error 1
> Makefile:135: *** OpenBLAS: Detecting CPU failed. Please set TARGET explicitly, e.g. make TARGET=your_cpu_target. Please read README for the detail..  Stop.
> make[2]: Leaving directory '/<<BUILDDIR>>/openblas-0.3.3+ds'
> make[1]: *** [debian/rules:77: override_dh_auto_build] Error 2
> make[1]: Leaving directory '/<<BUILDDIR>>/openblas-0.3.3+ds'
> make: *** [debian/rules:74: binary-arch] Error 2
> dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2
> --------------------------------------------------------------------------------
> 
> The error message says it all: Please set TARGET explicitly.
> 
> The fact that this package tries to detect the CPU is probably the
> reason the executables built in buildd.debian.org do not work
> everywhere:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743490
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781998
> 
> which in addition to the FTBFS bug, it's also a baseline violation.

As mentioned in the package description, on amd64, arm64 and i386, the
binary contains specialized kernels for many different micro-
architectures, and the selection  of the kernel is done at runtime. So
the design is correct and there is no baseline violation.

Still there seems to be an issue with your specific build environment,
and of course this is a bug (but maybe not an RC one, since you are the
first to report such a build failure after many years). Could you give
more details about the hardware you are using?

Thanks,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄⠀⠀⠀⠀  http://www.debian.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/debian-science-maintainers/attachments/20190302/6cb2eeeb/attachment.sig>