[issue6299] pyexpat build failure on Solaris 10 for 2.6.1/2.6.2

2014-02-04 Thread koobs
koobs added the comment: The issue applies and is reproducible for all versions 2.6 through 3.5. This is the changeset we applied to all FreeBSD Ports to fix the issue: https://svnweb.freebsd.org/ports?view=revisionrevision=326729 One specific example (Python 3.3): 1) Use CPPFLAGS over

[issue6299] pyexpat build failure on Solaris 10 for 2.6.1/2.6.2

2014-02-04 Thread koobs
koobs added the comment: Setting versions to correctly reflect those affected. -- versions: +Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6299

[issue6299] pyexpat build failure on Solaris 10 for 2.6.1/2.6.2

2014-02-04 Thread STINNER Victor
Changes by STINNER Victor victor.stin...@gmail.com: -- nosy: +haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6299 ___ ___ Python-bugs-list

[issue6299] pyexpat build failure on Solaris 10 for 2.6.1/2.6.2

2014-02-04 Thread koobs
koobs added the comment: Adding a patch for reference only -- keywords: +patch Added file: http://bugs.python.org/file33902/python-issue6299.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6299

[issue6299] pyexpat build failure on Solaris 10 for 2.6.1/2.6.2

2014-02-04 Thread STINNER Victor
Changes by STINNER Victor victor.stin...@gmail.com: -- versions: -Python 2.6, Python 3.1, Python 3.2, Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6299 ___

[issue6299] pyexpat build failure on Solaris 10 for 2.6.1/2.6.2

2014-02-03 Thread Mark Lawrence
Changes by Mark Lawrence breamore...@yahoo.co.uk: -- nosy: -BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6299 ___ ___

[issue6299] pyexpat build failure on Solaris 10 for 2.6.1/2.6.2

2014-02-03 Thread Tim Mooney
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's build

[issue6299] pyexpat build failure on Solaris 10 for 2.6.1/2.6.2

2013-09-01 Thread koobs
Changes by koobs koobs.free...@gmail.com: -- nosy: +koobs ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6299 ___ ___ Python-bugs-list mailing list

[issue6299] pyexpat build failure on Solaris 10 for 2.6.1/2.6.2

2013-05-21 Thread Mark Lawrence
Mark Lawrence added the comment: Is this still a problem given that both Python and Solaris have moved on? -- nosy: +BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6299 ___

[issue6299] pyexpat build failure on Solaris 10 for 2.6.1/2.6.2

2010-01-06 Thread Tim Mooney
Tim Mooney enchan...@users.sourceforge.net 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

[issue6299] pyexpat build failure on Solaris 10 for 2.6.1/2.6.2

2009-06-17 Thread Tim Mooney
New submission from Tim Mooney enchan...@users.sourceforge.net: 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