Tim Mooney added the comment:
Sooo It's been 3 years. Brian's patch has bit-rotted a bit, but it's easy
to update for recent Python.
What are the hold-ups to getting this applied?
--
___
Python tracker
<http://bugs.pyt
Tim Mooney added the comment:
I just tried Python 2.7.6 on x86_64-pc-openindiana151a9. The core issue is
still present. It's not currently causing a build failure, but only because
OpenIndiana 151a9 and Python are using the exact same version of Expat, so the
headers that python&#x
Tim Mooney added the comment:
For what it's worth, I've been using a patch nearly identical to this one with
python 2.6.x and 2.7.x with good success, and in my case it was under Solaris
10 with the no-cost "oss" package from 4Front. I now have a new workstation
Tim Mooney added the comment:
This still happens in 2.6.3 and 2.6.4 so I spent some time looking at it.
It's happening because of a combination of issues, but ultimately it's because
python's build isn't making certain that it's including its private copy of
exp
New submission from Tim Mooney :
I've built Python 2.6.1 and Python 2.6.2 on x86_64-sun-solaris2.10 using
the Sun Workshop Express (200903) toolchain. I'm building in 64 bit mode.
Most stuff builds just fine (even warnings are rare), but pyexpat fails
to link with this error:
Tim Mooney added the comment:
Solaris has both traditional System V curses and an XPG4-compatible
curses that does include mvwchgat. The traditional system V curses is
the default, for backward compatibility.
If you want the XPG4 compatible curses, you need to make sure
-I/usr/xpg4/include
Tim Mooney <[EMAIL PROTECTED]> added the comment:
I agree with Terry's comment -- Python's build machinery for multi-abi
systems is suboptimal, but documenting some methods that work for some
people would at least help.
--
nosy: +enchanter
_
Tim Mooney <[EMAIL PROTECTED]> added the comment:
Paul, your comment in your patch, about this being fixed post Solaris 9,
doesn't appear to be correct. I have x86_64-sun-solaris2.10 with all
patches applied and the problem exists there too. I'm using Workshop 12.
--
