Le vendredi 29 mai 2020 à 01:13 +0000, Mo Zhou a écrit : > Clarification: possibly a Ubuntu bug
> The way to reproduce with nspawn/chroot + ubuntu focal (20.04) > if you don't have docker > > 1. mkdir Focal > 2. debootstrap focal Focal/ > 3. systemd-nspawn -D Focal > 4. apt update -y; apt upgrade -y > 5. apt install -y r-base-core > 6. Rscript -e "example(solve)" # good with netlib > 7. apt install -y libopenblas-dev > 8. Rscript -e "example(solve)" # hang > > The way to reproduce with *. + debian > > 1. Not yet reproducible. Thanks Mo for spotting this. Indeed I can replicate the bug in a focal chroot, but not in a sid chroot. Moreover, if I install the Debian binary package for libopenblas0- pthread (0.3.8+ds-1) on top of a focal chroot, then the bug disappears. Since Ubuntu did not modify the Debian source package, it means that it’s the way of generating the openblas binary within Ubuntu that causes the bug. Compilation flags (as given by dpkg-buildflags) are currently the same between Debian and Ubuntu, so it does not come from that. Maybe this has to do with internal default flags of GCC? Or some other factor in the toolchain? I’m not familiar enough with Ubuntu to be able to answer that. -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄⠀⠀⠀⠀ https://www.debian.org
signature.asc
Description: This is a digitally signed message part
