Traceback (most recent call last): File "/var/tmp/portage/dev-lang/python-3.13.0_rc2/work/Python-3.13.0rc2/Lib/test/test_threading.py", line 1633, in test_recursion_limit self.assertEqual(p.returncode, 0, "Unexpected error: " + stderr.decode()) ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AssertionError: -11 != 0 : Unexpected error: Reproducible: Always
Created attachment 902497 [details] emerge --info
Created attachment 902498 [details] build.log
Does this still reproduce with: * plain CFLAGS? (-O2 -pipe) * glibc?
I'm not sure about glibc, but it seems like LTO is causing this error. Still even with plain CFLAGS I'm getting another error: ERROR: test_makedev (test.test_posix.PosixTester.test_makedev) ---------------------------------------------------------------------- Traceback (most recent call last): File "/var/tmp/portage/dev-lang/python-3.13.0_rc2/work/Python-3.13.0rc2/Lib/test/test_posix.py", line 730, in test_makedev self.assertEqual(posix.major(NODEV), NODEV) ~~~~~~~~~~~^^^^^^^ OverflowError: can't convert negative int to unsigned Should I report it as a separate bug?
(In reply to Piotr Kubaj from comment #4) > I'm not sure about glibc, but it seems like LTO is causing this error. > > Still even with plain CFLAGS I'm getting another error: > ERROR: test_makedev (test.test_posix.PosixTester.test_makedev) > ---------------------------------------------------------------------- > Traceback (most recent call last): > File > "/var/tmp/portage/dev-lang/python-3.13.0_rc2/work/Python-3.13.0rc2/Lib/test/ > test_posix.py", line 730, in test_makedev > self.assertEqual(posix.major(NODEV), NODEV) > ~~~~~~~~~~~^^^^^^^ > OverflowError: can't convert negative int to unsigned > > Should I report it as a separate bug? Yes, separate failure needs to be a separate bug. Can you remove all of the extra flags and try with just plain flags plus -flto=auto? A lot of those come from the old lto-overlay which is supposed to be no longer necessary.
-O2 -pipe -flto=auto also fails.