[issue1099] Mac compile fails with pydebug and framework enabled

Changes by Elias Pipping : -- nosy: -pipping ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue1099] Mac compile fails with pydebug and framework enabled

Changes by Ronald Oussoren : -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker ___ _

[issue1099] Mac compile fails with pydebug and framework enabled

Roundup Robot added the comment: New changeset 7af5a9298251 by Ronald Oussoren in branch '3.1': Fixes #1099: Mac compile fails with pydebug and framework enabled http://hg.python.org/cpython/rev/7af5a9298251 New changeset e8679f07badd by Ronald Oussoren in branch '3.2': Issue #1099: Fix the bui

[issue1099] Mac compile fails with pydebug and framework enabled

Ronald Oussoren added the comment: The patch has a spurious backslash at the end of the $(CC) command, but should otherwise be OK. I'm currently running the testsuite in will later today push the fix to the repository. -- ___ Python tracker

[issue1099] Mac compile fails with pydebug and framework enabled

Ronald Oussoren added the comment: I've added a new patch which only updates makefile.pre.in. -- Added file: http://bugs.python.org/file21112/issue1099-v2.patch ___ Python tracker __

[issue1099] Mac compile fails with pydebug and framework enabled

Ronald Oussoren added the comment: Good catch, and that would also allow dropping the change to configure.in (which would only ensure that -isysroot gets defined correctly). -- ___ Python tracker _

[issue1099] Mac compile fails with pydebug and framework enabled

Ned Deily added the comment: The patch, as is, fixes another build failure mode that has been reported (http://article.gmane.org/gmane.comp.python.general/685151): ./configure --enable-framework ; make I verified that 3.2 builds without the patch fail on both 10.5 ppc and 10.4 ppc (10.4 fa

[issue1099] Mac compile fails with pydebug and framework enabled

Ronald Oussoren added the comment: The attached patch removes the call to libtool and always links the framework using gcc (as was already done for universal builds). With this patch I can build the framework using the following configure command-line on OSX 10.6: ../configure --with-pyde

[issue1099] Mac compile fails with pydebug and framework enabled

Ned Deily added the comment: Yes, it is still an issue for all active branches. I'm working on a patch for it. -- nosy: +ned.deily versions: +Python 2.7, Python 3.1, Python 3.2 -Python 3.0 ___ Python tracker

[issue1099] Mac compile fails with pydebug and framework enabled

Georg Brandl added the comment: Is this still relevant? -- nosy: +georg.brandl ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue1099] Mac compile fails with pydebug and framework enabled

Changes by Ronald Oussoren : -- assignee: -> ronaldoussoren nosy: +ronaldoussoren ___ Python tracker ___ ___ Python-bugs-list mailing

[issue1099] Mac compile fails with pydebug and framework enabled

cfr <[EMAIL PROTECTED]> added the comment: Still fails for me on OS X 10.4.11 with latest available xcode (2.5). This is on PPC with the current stable release of python (2.5.2). ---configure script--- ../configure \ --enable-framework \ LDFLAGS=-L/usr/local/lib \ CFLAGS=

[issue1099] Mac compile fails with pydebug and framework enabled

Elias Pipping <[EMAIL PROTECTED]> added the comment: Configuring with '--with-pydebug --enable-framework --enable-universalsdk' (and invoking make afterwards) certainly works now for me. I'm running XCode 3.1 -- or more importantly 'i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 54

[issue1099] Mac compile fails with pydebug and framework enabled

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: Can you please try XCode 2.5? See issue 3533 for a report that says that upgrading solved the problem. -- nosy: +loewis ___ Python tracker <[EMAIL PROTECTED]> __

[issue1099] Mac compile fails with pydebug and framework enabled

Changes by Sean Reifschneider: -- priority: -> normal __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue1099] Mac compile fails with pydebug and framework enabled

Humberto Diogenes added the comment: I'm using these versions: intel: macosx 10.4.10, xcode 2.4.1 (gcc 4.0.1 build 5367) Tried again with current revision (58153) and with --enable-universalsdk it built just fine. Without it, I still get the same error. __ Track

[issue1099] Mac compile fails with pydebug and framework enabled

Elias Pipping added the comment: powerpc : macosx 10.4.10, xcode 2.4.1 (gcc 4.0.1 build 5367) intel : macosx 10.4.10, xcode 2.5pre (gcc 4.0.1 build 5370) __ Tracker <[EMAIL PROTECTED]> __ _

[issue1099] Mac compile fails with pydebug and framework enabled

Bill Janssen added the comment: Which versions of OS X, please? And which Xcode versions? -- nosy: +janssen __ Tracker <[EMAIL PROTECTED]> __ _

[issue1099] Mac compile fails with pydebug and framework enabled

Elias Pipping added the comment: I can reproduce this problem on both an intel and a powerpc mac. With '--with-pydebug --enable-framework --enable-universalsdk', the behavior is very much different: On a powerpc mac, configure fails with 'checking size of wchar_t...configure: error: cannot c

[issue1099] Mac compile fails with pydebug and framework enabled

New submission from Humberto Diogenes: Running this on Mac OS X: $ ./configure --with-pydebug --enable-framework $ make I get this: (...) ar cr libpython3.0.a Modules/config.o Modules/getpath.o Modules/main.o Modules/gcmodule.o ar cr libpython3.0.a Modules/threadmodule.o Modules/signalmodule.