[issue32597] Bad detection of clang

2018-01-19 Thread bapt
Change by bapt <b...@freebsd.org>: -- nosy: +vstinner ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32597> ___ ___ Python

[issue32597] Bad detection of clang

2018-01-19 Thread bapt
New submission from bapt <b...@freebsd.org>: When building modules and trying to set the proper linker flags for the library runtime path, the detection of the compiler is wrong. the issue: https://bugs.python.org/issue20767 was showing the issue and imho badly fixed. Clang behave li

[issue30647] CODESET error on AMD64 FreeBSD 10.x Shared 3.x caused by the PEP 538

2017-06-13 Thread bapt
bapt added the comment: More details here: C.UTF-8 is a glibc only thing: https://sourceware.org/glibc/wiki/Proposals/C.UTF-8 not even mainstream. The closest thing to a C locale with unicode would be to set everything to locale C but LC_CTYPE which would be set to en_US.UTF-8. The problem

[issue30647] CODESET error on AMD64 FreeBSD 10.x Shared 3.x caused by the PEP 538

2017-06-13 Thread bapt
bapt added the comment: Per POSIX, the C locale is only expected to be ASCII. C.UTF-8 is a linux only thing (actually I thought it was a debian only thing, but maybe not). I was thinking about creating a C.utf8 locale on FreeBSD but it is not that simple to do (still doable and an interesting

[issue25809] "Invalid" tests on locales

2015-12-05 Thread bapt
New submission from bapt: the locale tests the return value of locale functions against known good values. The problem is when those known good values becomes wrong because of an update of the locales. For example in recent CLDR definition the french separator for thousands in a &quo

[issue23817] Consider FreeBSD like any other OS in SOVERSION

2015-03-31 Thread bapt
bapt added the comment: Adding a patch on configure.ac (I bet configure should not be patched but regenerated) Considering the comment here: http://bugs.python.org/issue1044395#msg47064 about ldconfig(1) the output of ldconfig(1) is buggy in that regard, and the ports tree does not depends

[issue23817] Consider FreeBSD like any other OS in SOVERSION

2015-03-31 Thread bapt
New submission from bapt: In the configuration script: https://hg.python.org/cpython/file/47b2d1ff9743/configure.ac#l963 There is a special treatment done for FreeBSD, which is not needed, FreeBSD is perfectly fine with multiple digit in soversion. -- components: Build messages

[issue23817] Consider FreeBSD like any other OS in SOVERSION

2015-03-31 Thread bapt
bapt added the comment: Provide more information: Here is a description of the problem with the FreeBSD ldconfig(1) problem and why it was a problem with libpython.so.* https://wiki.freebsd.org/ports/fix_lib_depends Here is the commit that adds the new methode for ports to lookup

[issue23817] Consider FreeBSD like any other OS in SOVERSION

2015-03-31 Thread bapt
bapt added the comment: I do not think it is worth changing python 2.7 or python 3.4 given the fact that the .so.1 symlink is not created (which imho it should be a good idea to create but let's go step by step) Let's just do it for next python