This is a bit complicated to describe. When emerging Ardour, a lot of times this and similar error message appears: parsing /var/tmp/portage/media-sound/ardour-4.4/work/ardour-4.4/libs/pbd/pbd/fastlog.h failed together with: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 528: ordinal not in range(128) Nevertheless the package builds and seems to run fine. I file this bug, because the amount of (big red) error messages on the console is huge and I'm quite sure, this is a non wanted behaviour. # cat build.log | grep UnicodeDecodeError | wc -l 1080 Reproducible: Always Steps to Reproduce: 1. Install Ardour 4.4 with enabled Python 3.4. Actual Results: Strange Python parsing errors appear. Expected Results: No Python parsing error appears. Some information about my Python environment: # eselect python list Available Python interpreters: [1] python2.7 [2] python3.3 [3] python3.4 * [4] python3.5 # echo $LANG de_DE.UTF8 # python >>> import sys >>> sys.getfilesystemencoding() 'utf-8' Also it is eye-catching, that all source files are ASCII but the ones, that appears in the error message are utf-8, e.g. the above mentioned fastlog.h contains a copyright sign (©). Also I've tested to open the fastlog.h file, like this: >>> with open("fastlog.h") as f: ... for line in f: ... print(line) This runs without error.
Created attachment 417896 [details] build.log.gz
Hi Gerion, thanks for reporting, this issue is worked around with the fixes from bug #571734 (setting the shebang to python-2.7).
