[issue38204] Cannot compile on RPi with optimizations
Thomas Knox added the comment: I updated binutils: pi@pi4b:~/Downloads/Python-3.8.0b4 $ ld --version GNU ld (GNU Binutils) 2.32 Same problem. -- ___ Python tracker <https://bugs.python.org/issue38204> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38204] Cannot compile on RPi with optimizations
Thomas Knox added the comment: I'll be more than happy to buy you an RPi to do testing on. -- ___ Python tracker <https://bugs.python.org/issue38204> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38204] Cannot compile on RPi with optimizations
Thomas Knox added the comment: pi@pi4b:~ $ gcc --version gcc (Raspbian 8.3.0-6+rpi1) 8.3.0 pi@pi4b:~ $ ld --version GNU ld (GNU Binutils for Raspbian) 2.31.1 -- ___ Python tracker <https://bugs.python.org/issue38204> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38204] Cannot compile on RPi with optimizations
New submission from Thomas Knox : Trying to compile 3.8.0b4 on an raspberry pi 3B+ and 4 running: pi@pi4b:~/Downloads/Python-3.8.0b4 $ uname -a Linux pi4b 4.19.66-v7l+ #1253 SMP Thu Aug 15 12:02:08 BST 2019 armv7l GNU/Linux Using arguments: ./configure --disable-shared --enable-optimizations --enable-loadable-sqlite-extensions --enable-ipv6 --enable-big-digits --with-lto --with-doc-strings --with-ensurepip --with-openssl=/usr fails compilation at the linking stage with the errors: /usr/bin/ld: /usr/bin/ld: DWARF error: offset (7602768) greater than or equal to .debug_str size (517480) /usr/bin/ld: DWARF error: offset (2013417729) greater than or equal to .debug_str size (517480) /usr/bin/ld: DWARF error: offset (1375799296) greater than or equal to .debug_str size (517480) /usr/bin/ld: DWARF error: offset (3959620946) greater than or equal to .debug_str size (517480) /usr/bin/ld: DWARF error: offset (150994953) greater than or equal to .debug_str size (517480) /usr/bin/ld: DWARF error: offset (622700) greater than or equal to .debug_str size (517480) /usr/bin/ld: DWARF error: offset (990813185) greater than or equal to .debug_str size (517480) /usr/bin/ld: DWARF error: could not find abbrev number 9630 /tmp/ccX29Gpf.lto.o: in function `copy_base': :(.text+0x8374): undefined reference to `__gcov_one_value_profiler_atomic' /usr/bin/ld: :(.text+0x8388): undefined reference to `__gcov_average_profiler_atomic' /usr/bin/ld: :(.text+0x8398): undefined reference to `__gcov_ior_profiler_atomic' /usr/bin/ld: :(.text+0x840c): undefined reference to `__gcov_one_value_profiler_atomic' /usr/bin/ld: :(.text+0x8420): undefined reference to `__gcov_average_profiler_atomic' /usr/bin/ld: :(.text+0x8430): undefined reference to `__gcov_ior_profiler_atomic' /usr/bin/ld: :(.text+0x84c8): undefined reference to `__gcov_one_value_profiler_atomic' /usr/bin/ld: :(.text+0x84dc): undefined reference to `__gcov_average_profiler_atomic' /usr/bin/ld: :(.text+0x84ec): undefined reference to `__gcov_ior_profiler_atomic' /usr/bin/ld: :(.text+0x856c): undefined reference to `__gcov_one_value_profiler_atomic' /usr/bin/ld: :(.text+0x8580): undefined reference to `__gcov_average_profiler_atomic' /usr/bin/ld: :(.text+0x8590): undefined reference to `__gcov_ior_profiler_atomic' /usr/bin/ld: :(.text+0x866c): undefined reference to `__gcov_one_value_profiler_atomic' /usr/bin/ld: :(.text+0x867c): undefined reference to `__gcov_average_profiler_atomic' /usr/bin/ld: :(.text+0x868c): undefined reference to `__gcov_ior_profiler_atomic' /usr/bin/ld: :(.text+0x8718): undefined reference to `__gcov_one_value_profiler_atomic' /usr/bin/ld: :(.text+0x8728): undefined reference to `__gcov_average_profiler_atomic' /usr/bin/ld: :(.text+0x8738): undefined reference to `__gcov_ior_profiler_atomic' /usr/bin/ld: :(.text+0x87b0): undefined reference to `__gcov_one_value_profiler_atomic' /usr/bin/ld: :(.text+0x87c8): undefined reference to `__gcov_average_profiler_atomic' /usr/bin/ld: :(.text+0x87d8): undefined reference to `__gcov_ior_profiler_atomic' ... For hundreds of lines. Removing the --enable-optimizations flag allows it compile and link. -- components: Build messages: 352668 nosy: DNSGeek priority: normal severity: normal status: open title: Cannot compile on RPi with optimizations type: compile error versions: Python 3.7, Python 3.8 ___ Python tracker <https://bugs.python.org/issue38204> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37595] Python 3.7.4 does not build on Raspbian Buster
Thomas Knox added the comment: Any update on this? This is biting me too. I've tested on a Raspberry Pi 3B+, a 4B and a Zero W all running buster. All of them exhibit this same behavior. Also, this same error is preventing Python 2.7.16 from compiling on the same hardware. -- nosy: +DNSGeek ___ Python tracker <https://bugs.python.org/issue37595> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue36369] test_weakref super slow on RPi Zero
New submission from Thomas Knox : When building Python 3.7.2 on a Raspberry Pi Zero W, it takes over 6 hours to run test_weakref, and almost 15 hours total to run through all the tests. 14:28:14 load avg: 1.00 [396/416] test_weakset -- test_weakref passed in 6 hour 24 min Does it really need to take this long for one test? -- components: Tests messages: 338390 nosy: DNSGeek priority: normal severity: normal status: open title: test_weakref super slow on RPi Zero versions: Python 3.7 ___ Python tracker <https://bugs.python.org/issue36369> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue31962] test_importlib double free or corruption
Change by Thomas Knox : -- components: +Tests ___ Python tracker <https://bugs.python.org/issue31962> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue31962] test_importlib double free or corruption
New submission from Thomas Knox : On a Raspberry Pi 3 running Linux pi3 4.9.58-v7+ #1046 SMP Tue Oct 24 17:07:15 BST 2017 armv7l GNU/Linux C(PP)FLAGS="-O6 -march=armv8-a+crc -mtune=cortex-a53 -mfpu=crypto-neon-fp-armv8 -mfloat-abi=hard -ftree-vectorize" Built with ./configure --enable-loadable-sqlite-extensions --enable-optimizations --disable-shared --with-lto --enable-ipv6 --with-threads When the build phase is ... Running code to generate profile data (this can take a while): make run_profile_task make[1]: Entering directory '/home/pi/Downloads/Python-3.6.3' : # FIXME: can't run for a cross build ./python -m test.regrtest --pgo || true Run tests sequentially ... It errors and dies with 0:23:56 load avg: 0.87 [176/405] test_importlib *** Error in `./python': double free or corruption (!prev): 0x014166e0 *** Fatal Python error: Aborted Thread 0x685ff460 (most recent call first): File "", line 98 in acquire File "/home/pi/Downloads/Python-3.6.3/Lib/test/test_importlib/test_locks.py", line 83 in _acquire File "/home/pi/Downloads/Python-3.6.3/Lib/test/test_importlib/test_locks.py", line 93 in f File "/home/pi/Downloads/Python-3.6.3/Lib/test/lock_tests.py", line 38 in task Thread 0x76f04000 (most recent call first): File "/home/pi/Downloads/Python-3.6.3/Lib/test/lock_tests.py", line 17 in _wait File "/home/pi/Downloads/Python-3.6.3/Lib/test/lock_tests.py", line 56 in wait_for_finished File "/home/pi/Downloads/Python-3.6.3/Lib/test/test_importlib/test_locks.py", line 99 in run_deadlock_avoidance_test File "/home/pi/Downloads/Python-3.6.3/Lib/test/test_importlib/test_locks.py", line 113 in test_no_deadlock File "/home/pi/Downloads/Python-3.6.3/Lib/unittest/case.py", line 605 in run File "/home/pi/Downloads/Python-3.6.3/Lib/unittest/case.py", line 653 in __call__ File "/home/pi/Downloads/Python-3.6.3/Lib/unittest/suite.py", line 122 in run File "/home/pi/Downloads/Python-3.6.3/Lib/unittest/suite.py", line 84 in __call__ File "/home/pi/Downloads/Python-3.6.3/Lib/unittest/suite.py", line 122 in run File "/home/pi/Downloads/Python-3.6.3/Lib/unittest/suite.py", line 84 in __call__ File "/home/pi/Downloads/Python-3.6.3/Lib/unittest/suite.py", line 122 in run File "/home/pi/Downloads/Python-3.6.3/Lib/unittest/suite.py", line 84 in __call__ File "/home/pi/Downloads/Python-3.6.3/Lib/unittest/suite.py", line 122 in run File "/home/pi/Downloads/Python-3.6.3/Lib/unittest/suite.py", line 84 in __call__ File "/home/pi/Downloads/Python-3.6.3/Lib/unittest/suite.py", line 122 in run File "/home/pi/Downloads/Python-3.6.3/Lib/unittest/suite.py", line 84 in __call__ File "/home/pi/Downloads/Python-3.6.3/Lib/test/support/__init__.py", line 1765 in run File "/home/pi/Downloads/Python-3.6.3/Lib/test/support/__init__.py", line 1889 in _run_suite File "/home/pi/Downloads/Python-3.6.3/Lib/test/support/__init__.py", line 1933 in run_unittest File "/home/pi/Downloads/Python-3.6.3/Lib/test/libregrtest/runtest.py", line 172 in test_runner File "/home/pi/Downloads/Python-3.6.3/Lib/test/libregrtest/runtest.py", line 173 in runtest_inner File "/home/pi/Downloads/Python-3.6.3/Lib/test/libregrtest/runtest.py", line 137 in runtest File "/home/pi/Downloads/Python-3.6.3/Lib/test/libregrtest/main.py", line 378 in run_tests_sequential File "/home/pi/Downloads/Python-3.6.3/Lib/test/libregrtest/main.py", line 457 in run_tests File "/home/pi/Downloads/Python-3.6.3/Lib/test/libregrtest/main.py", line 535 in _main File "/home/pi/Downloads/Python-3.6.3/Lib/test/libregrtest/main.py", line 509 in main File "/home/pi/Downloads/Python-3.6.3/Lib/test/libregrtest/main.py", line 584 in main File "/home/pi/Downloads/Python-3.6.3/Lib/test/regrtest.py", line 46 in _main File "/home/pi/Downloads/Python-3.6.3/Lib/test/regrtest.py", line 50 in File "/home/pi/Downloads/Python-3.6.3/Lib/runpy.py", line 85 in _run_code File "/home/pi/Downloads/Python-3.6.3/Lib/runpy.py", line 193 in _run_module_as_main Aborted Every time. These exact same parameters and flags worked with 3.6.2 with no issue, but they die on 3.6.3 -- components: Build messages: 305676 nosy: DNSGeek priority: normal severity: normal status: open title: test_importlib double free or corruption type: crash versions: Python 3.6 ___ Python tracker <https://bugs.python.org/issue31962> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29889] test_asyncio fails always
Thomas Knox added the comment: The build succeeds, but the profile generation fails (only the test_asyncio portion fails), then does a new profiled build after the profiling run completes which succeeds. Then, when doing a 'make install', it builds the entire thing again and runs another profile generation run which also fails, then a new profiled build. Possibly because the first profile run failed? On an RPi, this is exceedingly painful as a build/profile/build cycle takes about 10 hours. So doing it twice is double-unfun. -- ___ Python tracker <http://bugs.python.org/issue29889> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29889] test_asyncio fails always
Thomas Knox added the comment: I changed the configuration flags to be: pi@pi3:~/Source/Python-3.6.1 $ ./configure --enable-optimizations --enable-loadable-sqlite-extensions --disable-ipv6 --with-system-expat --with-system-ffi --with-threads The profiling filed again with: 0:04:47 [ 25/405] test_asyncio Executing .start() done, defined at /home/pi/Source/Python-3.6.1/Lib/test/test_asyncio/test_pep492.py:150> result=None created at /home/pi/Source/Python-3.6.1/Lib/asyncio/base_events.py:446> took 1.187 seconds 0:08:45 [ 26/405] test_asyncore -- test_asyncio failed in 3 min 59 sec But at least it failed 2.5 minutes faster. :) -- ___ Python tracker <http://bugs.python.org/issue29889> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29889] test_asyncio fails always
New submission from Thomas Knox: Downloaded Python 3.6.1 source code onto CentOS 7.3 (64 bit), Fedora 25 (64 bit), Ubuntu 16.10 (64 bit) and Raspberry Pi 8.0 (32 bit). Configured with ./configure --enable-shared --enable-optimizations --enable-loadable-sqlite-extensions --disable-ipv6 --with-system-expat --with-system-ffi --with-threads On every platform, when running the profile generation code, test_asyncio fails with this error message: 0:06:45 [ 25/405] test_asyncio Executing .start() done, defined at /home/pi/Source/Python-3.6.1/Lib/test/test_asyncio/test_pep492.py:150> result=None created at /home/pi/Source/Python-3.6.1/Lib/asyncio/base_events.py:446> took 2.106 seconds 0:13:11 [ 26/405] test_asyncore -- test_asyncio failed in 6 min 27 sec -- components: Tests messages: 290059 nosy: Thomas Knox priority: normal severity: normal status: open title: test_asyncio fails always type: compile error versions: Python 3.6 ___ Python tracker <http://bugs.python.org/issue29889> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
