Path: csiph.com!newsfeed.xs4all.nl!newsfeed7.news.xs4all.nl!bofh.it!news.nic.it!robomod From: Andreas Tille Newsgroups: linux.debian.devel.mentors,linux.debian.maint.python,linux.debian.bugs.dist Subject: Re: scikit-learn in unstable FTBFS on arm64, armel, armhf, i386, ppc64el and s390x Date: Thu, 17 Feb 2022 13:50:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-mentors-request@lists.debian.org Thu Feb 17 12:42:18 2022 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.01 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DIGITS_LETTERS=1, LDO_WHITELIST=-5, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=unavailable autolearn_force=no X-Policyd-Weight: using cached result; rate: -4.6 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Mailing-List: archive/latest/107165 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/Yg5ClIJxaMfWJxMO@an3as.eu Approved: robomod@news.nic.it Lines: 51 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: 1003165@bugs.debian.org X-Original-Date: Thu, 17 Feb 2022 13:41:56 +0100 X-Original-Message-ID: X-Original-References: <164139193788.2513.7866707754451451433.reportbug@debian-sid.codehelp> <9bed8277-e65a-37e2-44b9-aa0f07dd6b0b@physik.fu-berlin.de> Xref: csiph.com linux.debian.devel.mentors:45231 linux.debian.maint.python:13951 linux.debian.bugs.dist:1093552 Hi, Am Wed, Feb 16, 2022 at 12:09:23PM +0100 schrieb John Paul Adrian Glaubitz: > > So, I have skimmed over the build logs and one of the main issues is the use of > -march flags to enforce a certain baseline [1]: > > powerpc64le-linux-gnu-gcc: error: unrecognized command-line option ‘-march=native’; did you mean ‘-mcpu=native’? > > This is a policy violation and must be fixed in any case. Blacklisting architectures > is not enough in this case as forcing the baseline of the buildds can lead to code > that won't run on the user's machines. I confirm this is a problem and the critical string can also be found in the amd64 build log[2]: ... running build_clib customize UnixCCompiler customize UnixCCompiler using build_clib CCompilerOpt.cc_test_flags[1013] : testing flags (-march=native) C compiler: x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC creating /tmp/tmpk22ehoi2/usr creating /tmp/tmpk22ehoi2/usr/lib creating /tmp/tmpk22ehoi2/usr/lib/python3 creating /tmp/tmpk22ehoi2/usr/lib/python3/dist-packages creating /tmp/tmpk22ehoi2/usr/lib/python3/dist-packages/numpy creating /tmp/tmpk22ehoi2/usr/lib/python3/dist-packages/numpy/distutils creating /tmp/tmpk22ehoi2/usr/lib/python3/dist-packages/numpy/distutils/checks compile options: '-c' extra options: '-march=native' CCompilerOpt.cc_test_flags[1013] : testing flags (-O3) C compiler: x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC ... I admit I'm not sure at what point / what tool might inject this string and I'm also not sure whether the option -march=native is really used in the amd64 case. Kind regards Andreas. > > [1] https://buildd.debian.org/status/fetch.php?pkg=scikit-learn&arch=ppc64el&ver=1.0.2-1&stamp=1644956229&raw=0 [2] https://buildd.debian.org/status/fetch.php?pkg=scikit-learn&arch=amd64&ver=1.0.2-1&stamp=1644952702&raw=0 -- http://fam-tille.de