[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 ___

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

Benjamin Peterson added the comment: I take it the build problem is because intl isn't a universal library? In that case, I think the best solution is to not define WITH_INTL if --enable-universalsdk is passed. Ronald, do you have an opinion? -- nosy: +ronaldoussoren __

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

Brett Cannon added the comment: So Evan's patch didn't work for me. But I did take Evan's point that LIBS was not being used in the framework build step and simply added $(LIBS) to Makefile.pre.in where the linking for the Python executable happens (attached a new patch with that in it). That go

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

Evan Behar added the comment: Nevermind, my bad. With Brett's patch, the build does not work with --enable-framework It appears that configure.in makes no assignment to FRAMEWORKLINK or AC_SUBST call with it, and so it is deposited in the final Makefile verbatim as @FRAMEWORKLINK@ If --enable

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

Brett Cannon added the comment: Didn't work when I turned on --enable-framework, but I have no clue how the framework build works so I am of no help with that. -- ___ Python tracker

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

Evan Behar added the comment: It works fine for my framework build on 10.4.11 -- ___ Python tracker ___ ___ Python-bugs-list mailing l

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

Benjamin Peterson added the comment: Does that fix framework builds, too? -- ___ Python tracker ___ ___ Python-bugs-list mailing list

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

Brett Cannon added the comment: I meant locale_fix2.patch causes the infinite output. Regardless, I now have my own patch that solves the problem. I simply make sure that if the check for intl passes it also added "-lintl" to $LIBS. You will need to run autoconf/autoheader yourself as when I ra

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

Benjamin Peterson added the comment: What about the third? -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: h

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

Brett Cannon added the comment: @Evan -- You need to edit configure.in and use autoconf to regenerate configure. @Benjamin -- your second patch leads to an infinite recursion or something with 'y\n' being printed out constantly. -- ___ Python tracke

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

Changes by Benjamin Peterson : Added file: http://bugs.python.org/file14161/locale_fix2.patch ___ Python tracker ___ ___ Python-bugs-list maili

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

Evan Behar added the comment: I applied Benjamin's new patch to the original files, but I receive the same error, and the LIBS in the Makefile still only has -ldl and not -lintl. -- ___ Python tracker _

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

Evan Behar added the comment: I think I've found the problem. In configure: 13830 if test "${ac_cv_lib_intl_textdomain+set}" = set; then 13831 echo $ECHO_N "(cached) $ECHO_C" >&6 13832 else 13833 ac_check_lib_save_LIBS=$LIBS 13834 LIBS="-lintl $LIBS" but then 13883 rm -f co

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

Benjamin Peterson added the comment: Here's another patch. -- Added file: http://bugs.python.org/file14159/locale_fix.patch ___ Python tracker ___ ___

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

Changes by Brett Cannon : -- stage: -> needs patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

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

Changes by Brodie Rao : -- nosy: +brodie ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/

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

Brett Cannon added the comment: I do have intl installed through MacPorts so I am sure Mark's right that having intl installed as well as running on OS X is triggering this. -- ___ Python tracker __

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

Mark Dickinson added the comment: I don't see Brett's failure with a straight './configure && make' issued from the top directory of a clean svn py3k checkout (r73082), but I do see it with: CC="gcc -I/opt/local/include -L/opt/local/lib" ./configure && make I'm on OS X 10.5.7, and have a Mac

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

Brett Cannon added the comment: Still fails because you are now no longer compiling against CoreFoundation. Probably need both CoreFoundation and intl: gcc -L/Users/brett/usr/lib -L/Users/brett/.local/lib -L/unix/lib -L/unix/macports/lib -L/Developer/usr/lib -lintl -o python.exe \

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

Erick Tryzelaar added the comment: Benjamin, I just applied that patch but I still got the same error: /usr/bin/libtool -o Python.framework/Versions/3.1/Python -dynamic libpython3.1.a \ -lSystem -lSystemStubs -arch_only i386 - install_name /opt/local/

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

Roumen Petrov added the comment: Benjamin, configure script check for function textdomain in libintl. -- nosy: +rpetrov ___ Python tracker ___ ___

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

Benjamin Peterson added the comment: Sorry to be pulling you into this, but would you see if this patch fixes your woes? -- keywords: +patch Added file: http://bugs.python.org/file14128/locale_fix.patch ___ Python tracker

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

New submission from Brett Cannon : I believe r72863 broke building on OS X. If you uncomment the ``-lintl`` part for _localemodule.c in Modules/Setup then Python 3.1 builds. Below is the linkage error that Tarek and I both independently ran into. gcc -L/Users/brett/usr/lib -L/Users/brett/.local/