[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl

Changes by Yitz Gale : -- nosy: +ygale ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/ma

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl

Changes by Brett Cannon : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl

Brett Cannon added the comment: OK, committed by configure.in patch along with Ronald's Makefile.pre.in patch in r73274. Thanks to everyone who helped out with this. Building sucks and autoconf doesn't always help. -- resolution: -> fixed stage: needs patch -> committed/rejected _

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl

Ronald Oussoren added the comment: The attached file libintl-framework-ronald.patch should do the trick. Could someone who is affected by this issue test this patch (and feel free to commit it if it works). I don't have libintl on my system and hence cannot test right now. -- Added f

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl

Roumen Petrov added the comment: The current check for *gettext/*textdomain* functions is not so correct. It mix(!?!) checks for headers with check for functions. GNU libc include them and on linux we will see in pyconfig.h (trunk): --- /* #undef WITH_LIBINTL */ #define HAVE_LIBINTL_H 1

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl

Changes by Brett Cannon : -- title: Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl -> Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl ___ Python tracker __

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl

Changes by Martin v. Löwis : Removed file: http://bugs.python.org/file14180/smime.p7s ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl

Changes by Martin v. Löwis : Removed file: http://bugs.python.org/file14181/smime.p7s ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl

Changes by Martin v. Löwis : Removed file: http://bugs.python.org/file14182/smime.p7s ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl

Changes by Martin v. Löwis : Removed file: http://bugs.python.org/file14183/smime.p7s ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl

Ronald Oussoren added the comment: On 4 Jun, 2009, at 2:24, Brett Cannon wrote: > > > Ronald, can you look at the changes I proposed on Makefile.pre.in to > make sure LIBS from configure get used in the framework builds? If you > do then that change with the configure.in change I suggested shoul

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl

Brett Cannon added the comment: As Benjamin said, this was failing on non-universal framework builds and just a regular build because '-lintl' was not getting added to LIBS in configure.in and LIBS was not being passed into the framework compile rule (for both universal and non-universal). As f

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl

Benjamin Peterson added the comment: There's a broader issue than just the non-universal intl problem. If intl.h is defined, then configure causes _localemodule.c to use functions from it, but it wasn't being linked to. -- ___ Python tracker

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl

Ronald Oussoren added the comment: On 4 Jun, 2009, at 0:59, Evan Behar wrote: > > Evan Behar added the comment: > > I haven't got any library issues using --enable-universalsdk, it won't > get to the linking stage becaue it doesn't find libintl.h > > And with --with-pydebug still doesn't build

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl

Ronald Oussoren added the comment: On 4 Jun, 2009, at 0:59, Benjamin Peterson wrote: > > Benjamin Peterson added the comment: > > 2009/6/3 Ronald Oussoren : >> >> Ronald Oussoren added the comment: >> >> I just noticed the update of the title. >> >> I propose to close this issue if this is ca

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl

Ronald Oussoren added the comment: On 4 Jun, 2009, at 0:59, Benjamin Peterson wrote: > > Benjamin Peterson added the comment: > > 2009/6/3 Ronald Oussoren : >> >> Ronald Oussoren added the comment: >> >> I just noticed the update of the title. >> >> I propose to close this issue if this is ca

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl

Ronald Oussoren added the comment: On 4 Jun, 2009, at 0:59, Evan Behar wrote: > > Evan Behar added the comment: > > I haven't got any library issues using --enable-universalsdk, it won't > get to the linking stage becaue it doesn't find libintl.h > > And with --with-pydebug still doesn't build

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl

Evan Behar added the comment: I haven't got any library issues using --enable-universalsdk, it won't get to the linking stage becaue it doesn't find libintl.h And with --with-pydebug still doesn't build because it won't find ___eprintf, whatever that is. The only version of libintl on my syste

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl

Benjamin Peterson added the comment: 2009/6/3 Ronald Oussoren : > > Ronald Oussoren added the comment: > > I just noticed the update of the title. > > I propose to close this issue if this is caused by a non-universal version > of libintl that's installed by macports. Actually, it can happen w

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl

Ronald Oussoren added the comment: I just noticed the update of the title. I propose to close this issue if this is caused by a non-universal version of libintl that's installed by macports. Macports can install universal binaries of its packages (the +universal variant), use that if you wan

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl

Benjamin Peterson added the comment: 2009/6/3 Ronald Oussoren : > > Ronald Oussoren added the comment: > > I have two procedural questions: > > 1) Who should I contact to get e-mail for all bugs that get tagged with > the Macintosh component? Create an issue on the meta tracker: http://psf.upf

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl

Ronald Oussoren added the comment: I have two procedural questions: 1) Who should I contact to get e-mail for all bugs that get tagged with the Macintosh component? 2) Please tag all mac-related bugs with the 'Macintosh' component, that's the one I most often check for new issues. -

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl

Ronald Oussoren added the comment: Do you have a copy of libintl in /usr/local or ~brett//local/lib? If so, could you run 'file' on that library to check if it is a universal library? All system libraries on OSX are universal binaries and work just fine with a universal build of Python, that

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl

Evan Behar added the comment: Curiously, if I define --with-pydebug I get ld: Undefined symbols: ___eprintf If I don't define --with-pydebug but I do use --enable-universalsdk I get a whole different problem: gcc -arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk -fno-strict-alia

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl

Changes by Benjamin Peterson : -- title: Python 3.1 rc1 will not build on OS X 10.5.7 -> Python 3.1 rc1 will not build on OS X 10.5.7 with macports libintl ___ Python tracker ___