Summary: | dev-python/fusil-1.3.2 fails to build with Python 3 and C/POSIX locale | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Johan Bergström <bugs> |
Component: | New packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | howard_b_golden |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Build log |
Description
Johan Bergström
2010-01-27 09:32:55 UTC
Created attachment 217570 [details]
Build log
Build log attached.
if i set an utf-8 locale before building, it works: # pwd /var/tmp/portage/dev-python/fusil-1.3.2/work/fusil-1.3.2-3.1 # export LC_ALL="en_US.utf-8" # python3.1 setup.py build running build running build_py creating build creating build/lib creating build/lib/fusil copying fusil/mockup.py -> build/lib/fusil copying fusil/application_logger.py -> build/lib/fusil <snip> copying and adjusting fuzzers/fusil-clamav -> build/scripts-3.1 copying and adjusting fuzzers/fusil-mplayer -> build/scripts-3.1 copying and adjusting fuzzers/fusil-firefox.bak -> build/scripts-3.1 copying and adjusting fuzzers/fusil-gimp.bak -> build/scripts-3.1 copying and adjusting fuzzers/fusil-libc-printf -> build/scripts-3.1 <snip> Should probably mention that fuzzers/fusil-libc-printf is the "offender" Actually Python 3 rather doesn't support C/POSIX locale. Maybe it would be sufficient to mention this fact in planned news entry for Python 3.1... (In reply to comment #4) s/news entry/news item/ Adding LC_ALL="en_US.utf-8" to /etc/paludis/bashrc allowed python3.1 to build fusil successfully. Question: Is this the best way to deal with this? (I wonder if changing LC_ALL Paludis-wide is going to cause other problems.) Is there some alternative way to just change LC_ALL for python3.1? C/POSIX locales are not supported. |