PyXPCOM build fails if python uses 4-byte unicode chars

RESOLVED FIXED

Status

()

Core
XPCOM
RESOLVED FIXED
14 years ago
11 years ago

People

(Reporter: Sebastian Tusk, Assigned: dougt)

Tracking

Trunk
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050110 Firefox/1.0 (Debian package 1.0+dfsg.1-2)
Build Identifier: 

The current implementation of PyXPCOM uses a set of functions (*UCS2) to convert
from and to python string objects.

These function are only present if python is build to use 2-byte unicode
characters. On many linux machines python is build with 4-byte unicode chars.
The build of pyXPCOM then fails with unresolved symbol errors for the mentioned
functions.

PyXPCOM should use public functions from the python library only. The *UCS2
function aren't public.

Reproducible: Always

Steps to Reproduce:
build PyXPCOM on debian/unstable
(Reporter)

Comment 1

14 years ago
Created attachment 173458 [details] [diff] [review]
patch writteb by Shane Hathaway

See http://aspn.activestate.com/ASPN/Mail/Message/pyxpcom/2484016 for a
discussion of the problem.

Comment 2

13 years ago
Best I can tell this patch has already been applied to the trunk, so is out of date.
(In reply to comment #2)
> Best I can tell this patch has already been applied to the trunk, so is out of
date.

Yes, the patch from bug 297598 incorporated this patch.

Comment 4

13 years ago
Closing as per comments.
Status: NEW → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → FIXED

Updated

11 years ago
Attachment #173458 - Flags: review?(mhammond)
You need to log in before you can comment on or make changes to this bug.