Can we just change the script to write a file instead of sending it's output through the shell? That should fix any encoding problems since the shell wont touch it and the LANG settings (no matter what they are) shouldn't matter.
Dylan Quoting Mathieu Bridon (2018-08-24 07:58:21) > Hi, > > On Thu, 2018-08-23 at 23:23 -0400, Ilia Mirkin wrote: > > This breaks the build for me. It selects python3 instead of python2, > > and gen_xmlpool.py bails out when trying to print \xf3 to stdout with > > a LANG=C locale. > > In general though, Python 3 works very badly with LANG=C. Upstream > Python recommends just not using LANG=C at all, and instead using a > UTF8 locale, like C.UTF-8 instead. > > In fact, starting with 3.7, Python will emit a big warning when it is > run on a non-UTF8 locale, and try to fallback to C.UTF-8 if it can. > > There might be something to fix in this case (I haven't had time to > look at it yet), but I'd still advise you try and use a UTF8 locale > when running Python scripts in the future, if at all possible. > > > -- > Mathieu > > _______________________________________________ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/mesa-dev
signature.asc
Description: signature
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
