Bug 414333 – dev-lang/python-3.2.3-r1 fails to build in non-unicode locale

• Status: RESOLVED OBSOLETE
• Product: Gentoo Linux

[Description Patrick Lauer 2012-05-02 05:57:45 UTC]

Skipping: RTLD_NEXT = ((void *) -1l)
Skipping: RTLD_DEFAULT = ((void *) 0)
Traceback (most recent call last):
  File "../../Tools/scripts/h2py.py", line 167, in <module>
    main()
  File "../../Tools/scripts/h2py.py", line 81, in main
    process(fp, outfp)
  File "../../Tools/scripts/h2py.py", line 108, in process
    line = fp.readline()
  File "/var/tmp/portage/dev-lang/python-3.2.3-r1/work/Python-3.2.3/Lib/encodings/ascii.py", line 26, in decode
    return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 175: ordinal not in range(128)
make: *** [platformspecificmods] Error 1
emake failed
 * ERROR: dev-lang/python-3.2.3-r1 failed (compile phase):
 *   emake failed
 * 
 * Call stack:
 *     ebuild.sh, line  85:  Called src_compile
 *   environment, line 5490:  Called die
 * The specific snippet of code:
 *       emake CPPFLAGS="" CFLAGS="" LDFLAGS="" || die "emake failed";
 * 
 * If you need support, post the output of 'emerge --info =dev-lang/python-3.2.3-r1',
 * the complete build log and the output of 'emerge -pqv =dev-lang/python-3.2.3-r1'.
 * The complete build log is located at '/var/tmp/portage/dev-lang/python-3.2.3-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-lang/python-3.2.3-r1/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-lang/python-3.2.3-r1/work/Python-3.2.3'
 * S: '/var/tmp/portage/dev-lang/python-3.2.3-r1/work/Python-3.2.3'


# eselect locale show
LANG variable in profile:
  (none)

[Comment 1 Juergen Rose 2012-05-02 11:11:08 UTC]

I have the same issue.

[Comment 2 Mike Gilbert 2012-05-02 14:51:17 UTC]

Added upstream bug report to URL.

python-3.2.3-r1 dropped 23_all_h2py_encoding.patch since it has not been accepted upstream. See discussion on the gentoo-python mailing list.

It seems pretty easy to trigger this problem, so we should probably rethink that decision. Thoughts?

[Comment 3 Dirkjan Ochtman (RETIRED) 2012-05-02 15:09:10 UTC]

3.2.2 doesn't have that patch either, does it?

I think rethinking it would be good, but let's also try to push harder upstream?

[Comment 4 Harris Landgarten 2012-05-02 15:15:21 UTC]

I have a unicode locale and can build with portage but get the same failures referenced using cave.

[Comment 5 André Terpstra 2012-05-02 15:16:28 UTC]

same issue here

[Comment 6 Mike Gilbert 2012-05-02 15:37:20 UTC]

(In reply to comment #3)
> 3.2.2 doesn't have that patch either, does it?

Correct. dev-lang/python-3.2.2-r1 builds successfully in the same environment without this patch.

> I think rethinking it would be good, but let's also try to push harder
> upstream?

That's always a good plan. I have not studied the problem well enough to express an intelligent opinion upstream, so that will take some time if I'm the one to do it.

[Comment 7 Mike Gilbert 2012-05-03 01:11:58 UTC]

I have reverted to the previous patchset, which restores 23_all_h2py_encoding.patch.

Let's leave this open until upstream moves on it.

[Comment 8 Patrick Lauer 2014-12-26 09:09:49 UTC]

And we've declared py3.2 dead, so this one is no longer something to worry about