[issue37595] Python 3.7.4 does not build on Raspbian Buster
Kal Sze added the comment: Yes, removing --enable-optimizations and keeping all other configure options allows me to build. However, I think most people *do* want optimizations, especially because the Raspberry Pi itself already isn't very fast. -- ___ 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
[issue37595] Python 3.7.4 does not build on Raspbian Buster
Kal Sze added the comment: Sorry, I meant most up-to-date version of binutils in Raspbian *Buster* in my previous message. -- ___ 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
[issue37595] Python 3.7.4 does not build on Raspbian Buster
Kal Sze added the comment: I looked at my build log again. The very first line that jumps out as abnormal is this: /usr/bin/ld: /usr/bin/ld: DWARF error: invalid abstract instance DIE ref A quick DuckDuckGoing suggests that this *may* be related to a broken version of binutils: https://lists.gnu.org/archive/html/bug-binutils/2018-07/msg00150.html The current, most up-to-date version of binutils in Raspbian Stretch is this: $ dpkg -l binutils Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-==-==--== ii binutils 2.31.1-16+rpi1 armhfGNU assembler, linker and binary utilities A quick grep of the output of `apt changelog binutils` doesn't mention the bug number (23425). I don't know what conclusion to draw. -- ___ 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
[issue37595] Python 3.7.4 does not build on Raspbian Buster
New submission from Kal Sze : Like the title says. Tried building with these `configure` options: --enable-optimizations \ --with-lto \ --enable-shared \ --enable-loadable-sqlite-extensions \ --enable-ipv6 \ --with-system-expat \ --with-system-ffi \ --with-system-libmpdec \ --with-doc-strings \ --with-pymalloc \ --with-c-locale-coercion \ --with-ensurepip=upgrade And `CFLAGS="-O3 -march=native"` But got this error message: ``` /usr/bin/ld: ./libpython3.7m.so: undefined reference to `__gcov_pow2_profiler_atomic' /usr/bin/ld: ./libpython3.7m.so: undefined reference to `__gcov_average_profiler_atomic' collect2: error: ld returned 1 exit status make[3]: *** [Makefile:733: Programs/_testembed] Error 1 make[3]: Leaving directory '/tmp/python-build.20190712163526.2762/Python-3.7.4' make[2]: *** [Makefile:521: build_all_generate_profile] Error 2 make[2]: Leaving directory '/tmp/python-build.20190712163526.2762/Python-3.7.4' make[1]: *** [Makefile:497: profile-gen-stamp] Error 2 make[1]: Leaving directory '/tmp/python-build.20190712163526.2762/Python-3.7.4' make: *** [Makefile:509: profile-run-stamp] Error 2 ``` -- components: Build files: python-build.20190711104717.24526.log messages: 347948 nosy: kal.sze priority: normal severity: normal status: open title: Python 3.7.4 does not build on Raspbian Buster type: compile error versions: Python 3.7 Added file: https://bugs.python.org/file48482/python-build.20190711104717.24526.log ___ 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
[issue34155] email.utils.parseaddr mistakenly parse an email
Kal Sze added the comment:
Another failure case:
>>> from email.utils import parseaddr
>>> parseaddr('fo@o...@bar.com')
('', 'fo@o')
If I understand the RFC correctly, the correct results should be ('', '')
because there are two '@' signs. The first '@' would need to be quoted for the
address to be valid.
--
nosy: +Kal Sze2
___
Python tracker
<https://bugs.python.org/issue34155>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34986] python finds test modules from the wrong directory during PGO build
Kal Sze added the comment: Oops, sorry for the noise. This is mostly a duplicate of #34985 because the crash log attachment was too big and caused the issue tracker's proxy server to return an error code, so I thought the initial bug report creation failed. An e-mail confirmation arrived only much later. -- resolution: -> duplicate stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue34986> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34986] python finds test modules from the wrong directory during PGO build
New submission from Kal Sze : OS: Ubuntu Desktop 18.04.1 x86-64 Python 3.7.0 When trying to build Python 3.7 from source, with the `--enable-shared --enable-optimizations --with-lto` configure options, python needs to run the test suite in order to generate PGO data. However, it turns out that it would find test modules from the wrong directory, if there is already another version of Python 3 installed system-wide (Ubuntu 18.04 comes with Python 3.6 pre-installed). I found out because Ubuntu's automatic crash reporter caught a core dump during `python -m tests.regrtest` and I could see that python found the tests.regrtest module at `/usr/lib/python3.6/test/regrtest.py`. In the end, the build is reported as "successful", I guess it's because the Makefile expects it the crash anyway. In any case, it still seems wrong because it means the wrong test suite is run. Ubuntu's crash report in raw format is attached, for anybody who knows how to read it (it's in plain text anyway) -- components: Build files: _usr_lib_python3.6_test_regrtest.py.1000.crash messages: 327726 nosy: Kal Sze2 priority: normal severity: normal status: open title: python finds test modules from the wrong directory during PGO build type: behavior versions: Python 3.7 Added file: https://bugs.python.org/file47868/_usr_lib_python3.6_test_regrtest.py.1000.crash ___ Python tracker <https://bugs.python.org/issue34986> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34985] python finds test modules from the wrong directory during PGO build
New submission from Kal Sze : OS: Ubuntu Desktop 18.04.1 x86-64 Python 3.7.0 When trying to build Python 3.7 from source, with the `--enable-shared --enable-optimizations --with-lto` configure options, python needs to run the test suite in order to generate PGO data. However, it turns out that it would find test modules from the wrong directory, if there is already another version of Python 3 installed system-wide (Ubuntu 18.04 comes with Python 3.6 pre-installed). I found out because Ubuntu's automatic crash reporter caught a core dump during `python -m tests.regrtest` and I could see that python found the tests.regrtest module at `/usr/lib/python3.6/test/regrtest.py`. In the end, the build is reported as "successful", I guess it's because the Makefile expects it the crash anyway. In any case, it still seems wrong because it means the wrong test suite is run. I have uploaded Ubuntu's crash report in raw format here, for anybody who knows how to read it (it's in plain text anyway): https://www.dropbox.com/s/6ihxoouoqe1k98f/_usr_lib_python3.6_test_regrtest.py.1000.crash?dl=0 -- components: Build messages: 327725 nosy: Kal Sze2 priority: normal severity: normal status: open title: python finds test modules from the wrong directory during PGO build type: behavior versions: Python 3.7 ___ Python tracker <https://bugs.python.org/issue34985> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
