Your message dated Wed, 2 Feb 2022 19:41:46 +0000
with message-id <[email protected]>
and subject line Re: sagemath: ftbfs with -march=x86-64-v2
has caused the Debian Bug report #983931,
regarding sagemath: ftbfs with -march=x86-64-v2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
983931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983931
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:sagemath
Version: 9.2-2
Severity: minor
User: [email protected]
Usertags: ftbfs-x86-64-v2
Starting with LLVM 12 and GCC 11 (and backported to gcc-10 for Debian),
GCC introduces optimizations for new micro-architecture levels from
the x86-64 psABI. Filing these bug reports for packages building with
the current level (x86-64), but not with x86-64-v2.
To reproduce these issues, append -march=x86-64-v2 to the compiler
flags (CFLAGS, CXXFLAGS, ...). You also need hardware supporting these.
The easiest way is to call the dynamic linker in glibc 2.33 like
/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 --help
Otherwise look at the flags in /proc/cpuinfo and compare these with
those from table 3.1 in the System V Application Binary Interface doc:
https://gitlab.com/x86-psABIs/x86-64-ABI/-/wikis/x86-64-psABI
Please don't upload a package setting these flags by default. The
x86-64 baseline is still unchanged.
The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc10-v2/sagemath_9.2-2_unstable_gcc10-v2.log
The last lines of the build log are at the end of this report.
[...]
sage -t --long --random-seed=0
src/sage/schemes/elliptic_curves/ell_rational_field.py # 1 doctest failed
sage -t --long --random-seed=0
src/sage/schemes/elliptic_curves/ell_number_field.py # 4 doctests failed
sage -t --long --random-seed=0 src/sage/schemes/elliptic_curves/kraus.py # 1
doctest failed
sage -t --long --random-seed=0 src/sage/schemes/elliptic_curves/ell_generic.py
# 1 doctest failed
sage -t --long --random-seed=0
src/sage/schemes/elliptic_curves/gal_reps_number_field.py # 1 doctest failed
sage -t --long --random-seed=0 src/sage/symbolic/expression.pyx # 2 doctests
failed
sage -t --long --random-seed=0 src/sage/structure/factorization.py # 4
doctests failed
sage -t --long --random-seed=0 src/sage/arith/misc.py # 2 doctests failed
sage -t --long --random-seed=0 src/sage/modules/torsion_quadratic_module.py #
3 doctests failed
sage -t --long --random-seed=0 src/sage/modules/fg_pid/fgp_element.py # 8
doctests failed
sage -t --long --random-seed=0 src/sage/modules/fg_pid/fgp_module.py # 30
doctests failed
sage -t --long --random-seed=0 src/sage/modules/fg_pid/fgp_morphism.py # 5
doctests failed
sage -t --long --random-seed=0 src/sage/interacts/test_jupyter.rst # 1 doctest
failed
sage -t --long --random-seed=0 src/sage/interfaces/tests.py # 2 doctests failed
sage -t --long --random-seed=0 src/sage/interfaces/giac.py # 4 doctests failed
sage -t --long --random-seed=0 src/sage/interfaces/sympy.py # 1 doctest failed
sage -t --long --random-seed=0 src/sage/geometry/cone.py # 1 doctest failed
sage -t --long --random-seed=0 src/sage/geometry/polyhedron/library.py # 1
doctest failed
sage -t --long --random-seed=0 src/sage/geometry/polyhedron/base.py # 1
doctest failed
sage -t --long --random-seed=0 src/sage/matrix/matrix_double_dense.pyx # 2
doctests failed
sage -t --long --random-seed=0 src/sage/matrix/matrix_integer_dense.pyx # 1
doctest failed
sage -t --long --random-seed=0 src/sage/numerical/mip.pyx # 1 doctest failed
sage -t --long --random-seed=0 src/sage/lfunctions/pari.py # 1 doctest failed
sage -t --long --random-seed=0 src/sage/rings/integer.pyx # 1 doctest failed
sage -t --long --random-seed=0 src/sage/rings/finite_rings/residue_field.pyx #
7 doctests failed
sage -t --long --random-seed=0 src/sage/rings/finite_rings/integer_mod_ring.py
# 1 doctest failed
sage -t --long --random-seed=0
src/sage/rings/finite_rings/finite_field_constructor.py # 2 doctests failed
sage -t --long --random-seed=0
src/sage/rings/number_field/number_field_ideal.py # 4 doctests failed
sage -t --long --random-seed=0 src/sage/rings/number_field/number_field.py # 1
doctest failed
sage -t --long --random-seed=0 src/sage/rings/number_field/class_group.py # 2
doctests failed
sage -t --long --random-seed=0 src/sage/rings/number_field/order.py # 1
doctest failed
sage -t --long --random-seed=0 src/sage/rings/number_field/unit_group.py # 10
doctests failed
sage -t --long --random-seed=0 src/sage/rings/number_field/S_unit_solver.py #
8 doctests failed
sage -t --long --random-seed=0
src/sage/rings/number_field/number_field_element.pyx # 3 doctests failed
sage -t --long --random-seed=0
src/sage/rings/number_field/number_field_ideal_rel.py # 1 doctest failed
sage -t --long --random-seed=0 src/sage/rings/number_field/number_field_rel.py
# 2 doctests failed
sage -t --long --random-seed=0
src/sage/rings/polynomial/polynomial_quotient_ring.py # 1 doctest failed
sage -t --long --random-seed=0 src/sage/rings/polynomial/polynomial_element.pyx
# 1 doctest failed
sage -t --long --random-seed=0 src/sage/rings/polynomial/pbori/randompoly.py #
1 doctest failed
sage -t --long --random-seed=0 src/sage/modular/local_comp/smoothchar.py # 2
doctests failed
sage -t --long --random-seed=0 src/sage/modular/local_comp/liftings.py # 1
doctest failed
sage -t --long --random-seed=0 src/sage/modular/modsym/p1list_nf.py # 1
doctest failed
sage -t --long --random-seed=0 src/sage/repl/image.py # 4 doctests failed
sage -t --long --random-seed=0 src/sage/repl/ipython_kernel/interact.py # 1
doctest failed
sage -t --long --random-seed=0 src/sage/repl/ipython_kernel/install.py # 2
doctests failed
sage -t --long --random-seed=0 src/sage/repl/ipython_kernel/widgets_sagenb.py
# 1 doctest failed
sage -t --long --random-seed=0
src/sage/combinat/cluster_algebra_quiver/interact.py # 1 doctest failed
sage -t --long --random-seed=0
src/sage/combinat/cluster_algebra_quiver/cluster_seed.py # 1 doctest failed
sage -t --long --random-seed=0
src/sage/combinat/cluster_algebra_quiver/quiver.py # 1 doctest failed
sage -t --long --random-seed=0 src/sage/finance/time_series.pyx # 8 doctests
failed
sage -t --long --random-seed=0 src/sage/groups/fqf_orthogonal.py # 2 doctests
failed
sage -t --long --random-seed=0 src/sage/groups/abelian_gps/abelian_group.py #
1 doctest failed
sage -t --long --random-seed=0
src/sage/groups/additive_abelian/additive_abelian_group.py # 10 doctests failed
sage -t --long --random-seed=0 src/sage/graphs/generators/families.py # 1
doctest failed
----------------------------------------------------------------------
Total time for all tests: 909.1 seconds
cpu time: 839.1 seconds
cumulative wall time: 893.4 seconds
make[4]: Entering directory '/<<PKGBUILDDIR>>'
Error: 207 tests failed, up to 200 failures are tolerated
make[4]: *** [debian/rules:165: had-few-failures] Error 1
make[4]: Leaving directory '/<<PKGBUILDDIR>>'
make[3]: *** [debian/rules:202: override_dh_auto_test-arch] Error 2
make[3]: Leaving directory '/<<PKGBUILDDIR>>'
make[2]: *** [debian/rules:40: build] Error 2
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
make[1]: *** [debian/rules:40: install] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:40: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Version: sagemath/9.4-1
I think at the time of the bug report the build was failing anyway on all
architectures because of too many test failures (see #986527). It's fixed now
so I'm closing the bug.
Best,
Tobias
On Wed, 03 Mar 2021 15:13:12 +0000 Matthias Klose <[email protected]> wrote:
> Package: src:sagemath
> Version: 9.2-2
> Severity: minor
> User: [email protected]
> Usertags: ftbfs-x86-64-v2
>
> Starting with LLVM 12 and GCC 11 (and backported to gcc-10 for Debian),
> GCC introduces optimizations for new micro-architecture levels from
> the x86-64 psABI. Filing these bug reports for packages building with
> the current level (x86-64), but not with x86-64-v2.
>
> To reproduce these issues, append -march=x86-64-v2 to the compiler
> flags (CFLAGS, CXXFLAGS, ...). You also need hardware supporting these.
> The easiest way is to call the dynamic linker in glibc 2.33 like
> /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 --help
> Otherwise look at the flags in /proc/cpuinfo and compare these with
> those from table 3.1 in the System V Application Binary Interface doc:
> https://gitlab.com/x86-psABIs/x86-64-ABI/-/wikis/x86-64-psABI
>
> Please don't upload a package setting these flags by default. The
> x86-64 baseline is still unchanged.
>
> The full build log can be found at:
> http://people.debian.org/~doko/logs/20210228/filtered/gcc10-v2/sagemath_9.2-2_unstable_gcc10-v2.log
> The last lines of the build log are at the end of this report.
>
> [...]
--- End Message ---
