[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Benjamin Peterson added the comment: Fixed 3.1 in r79117. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ P

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Ned Deily added the comment: (2.6.5 -> Issue8175) -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Ned Deily added the comment: Per discussion with Ronald and Benjamin, attaching a revised patch (issue-sl-configure-32-31-rev3.txt) for 3.1 which ports the changes committed in r78813 and r78816 along with the Mac/README changes. In the process of producing the revised 3.1 patch, I discovered

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Changes by Ned Deily : -- versions: +Python 3.1 -Python 2.6 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Tom Loredo added the comment: > Unless you vehemently disagree, I am not making this a release blocker for > 2.6.5. I'm not sure who you are asking (I doubt it was me!), but I don't consider this a release blocker. The only possible substantive issue is whether "python" should run 32-bit or

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Barry A. Warsaw added the comment: Unless you vehemently disagree, I am not making this a release blocker for 2.6.5. -- priority: release blocker -> critical ___ Python tracker

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Tom Loredo added the comment: > the python-32 executable has never been linked into /usr/local/bin. What I meant by "the version pointed to" is: The "python" command in 2.6.4 produced by an "intel" universal build (whether in the framework or the install prefix) executed as 64-bit. I don't be

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Ronald Oussoren added the comment: On 15 Mar, 2010, at 16:22, Tom Loredo wrote: > > Tom Loredo added the comment: > > Ned- > > I *did* run "make install"; everything I reported was about the situation > *after* running "make install". In particular, I don't know any way to get > access t

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Tom Loredo added the comment: Ned- I *did* run "make install"; everything I reported was about the situation *after* running "make install". In particular, I don't know any way to get access to IDLE without "make install"; what I described came from using the version in Applications/Python

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Changes by Ned Deily : -- versions: +Python 3.1 -Python 2.6 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Ned Deily added the comment: Re-opening for 3.1.2: the corresponding fixes have not made it into 3.1.2 yet. -- status: closed -> open ___ Python tracker ___ _

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Barry A. Warsaw added the comment: As per msg100765, Ned confirms this is fixed for 2.6.5. -- status: open -> closed ___ Python tracker ___ __

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Ned Deily added the comment: You need to run 'make install'. The various "python-32" and "python-64" files are created and installed by the Mac/Makefile "install_python4way" target which should be getting called by the main Makefile "install" target as set by configure for the --with-univers

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Tom Loredo added the comment: Attempted to build 2.6.5rc2 on Mac Pro (2006), OS 10.6.2, following instructions in Mac/README: ./configure --prefix=/usr/local/tmp --enable-framework --with-universal-archs=intel --enable-universalsdk=/ Results of "make test" are as expected from past experienc

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Ned Deily added the comment: Looks good for 2.6.5 (with 10.6 'intel' build). -- ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Ronald Oussoren added the comment: Ned: I fixed the typo in r78816 -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Changes by Barry A. Warsaw : -- priority: high -> release blocker ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Ned Deily added the comment: Almost! There's a small but significant typo that needs to be fixed in the change (r78813) that was committed for 2.6: - UNIVERSAL_ARCH64_FLAGS="-arch x86_64 -arch x86_64" + UNIVERSAL_ARCH64_FLAGS="-arch x86_64 -arch ppc64" -- ___

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Barry A. Warsaw added the comment: Thanks for the fix guys. I believe this means it's no longer a blocker for 2.6.5rc2, right? -- priority: release blocker -> high versions: -Python 2.6 ___ Python tracker __

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Ronald Oussoren added the comment: I've commited a fix for 2.6 in r78813. I will port that fix to 3.1 later today, but don't have time to test right now. My fix is simular to the patch by Ned. -- ___ Python tracker

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Changes by Ned Deily : Removed file: http://bugs.python.org/file16505/issue-sl-configure-32-31.txt ___ Python tracker ___ ___ Python-bugs-list

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Ned Deily added the comment: Correct inadvertent deletion in the 3.1 Mac/README. -- Added file: http://bugs.python.org/file16506/issue-sl-configure-32-31-rev1.txt ___ Python tracker

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Changes by Ned Deily : Added file: http://bugs.python.org/file16505/issue-sl-configure-32-31.txt ___ Python tracker ___ ___ Python-bugs-list ma

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Ned Deily added the comment: The attached patches fix the problem for 2.6 and 3.1: 1. configure(.in) is changed to invoke the existing "4way" build targets for --with-universal-archs values of 3-way and intel as well as all. 2. configure(.in) passes the necessary lipo -extract arch values into

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Barry A. Warsaw added the comment: On Mar 08, 2010, at 08:20 PM, Ned Deily wrote: >(Ronald and I agree this should be a release-blocker. Patch to follow.) BTW, the right thing to do in this case (for 2.6 anyway) is to set the issue to be a release blocker, so it gets my attention. I can alway

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Changes by Barry A. Warsaw : -- priority: -> release blocker ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

New submission from Ned Deily : 2.6.5 release blocker 3.1.2 release blocker For 10.6, new universal build options were added to reflect the dropping of support in 10.6 for the ppc64 arch. The new options: --universal-archs=3-way -> -arch {i386,x86_64,ppc) --universal-archs=intel -> -arch