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

[Sébastien Villemot]

Control: forwarded -1 https://github.com/xianyi/OpenBLAS/issues/2048
Control: tags -1 + upstream
Control: severity -1 important

Le samedi 02 mars 2019 à 21:28 +0100, Santiago Vila a écrit :
> > 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?
> 
> I'm currently using Scaleway 1-XS and 1-S instances. On both types of
> instances the package always fail to build. I didn't find a way to
> move the "unbuildability property" to a non-failing machine (for
> example, by taking /proc/cpuinfo in the failing machine and using
> bind-mount on the non-failing machine), so I decided to report it anyway
> without a "recipe to reproduce it" but with an offer to ssh into a failing
> machine instead.

I've tried to fix the issue by myself on the host you provided me
access to, but without success so far. Hence I have forwarded it
upstream.

I am also downgrading the severity, since the FTBFS is specific to a
seemingly small subset of machines (and in particular it never occurred
on buildds).

Best,

-- 
⢀⣴⠾⠻⢶⣦⠀  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/20190307/d050e5ed/attachment.sig>