[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/issue38

[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> ___ ___

[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/issue38

[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

[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

[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

[issue31962] test_importlib double free or corruption

Change by Thomas Knox <tk...@mac.com>: -- components: +Tests ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue31962> ___ __

[issue31962] test_importlib double free or corruption

New submission from Thomas Knox <tk...@mac.com>: 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

[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

[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

[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