[issue7452] Invalid mnemonic 'fnstcw'

Changes by Ronald Oussoren : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue7452] Invalid mnemonic 'fnstcw'

Mark Dickinson added the comment: Yes, this can be closed as far as I'm concerned. -- ___ Python tracker ___ ___ Python-bugs-list mail

[issue7452] Invalid mnemonic 'fnstcw'

Ronald Oussoren added the comment: BTW. Am I correct when I state that this issue has been fixed and can be closed? -- ___ Python tracker ___ ___

[issue7452] Invalid mnemonic 'fnstcw'

Ronald Oussoren added the comment: Ned: the best way to ensure universal builds don't get broken is through the buildbots. AFAIK there are no buildbots that create universal binaries at the moment. Sadly enough I don't have the resources to provide one. Mark: Mac/README explains how to build

[issue7452] Invalid mnemonic 'fnstcw'

Ned Deily added the comment: Mark, I wasn't ranting at you or Ronald or anyone in particular. It's no secret that Python's build system is complex and fragile in some areas. On the other hand, the build system is ambitious, covering a wide variety of platforms and variants, and is largely s

[issue7452] Invalid mnemonic 'fnstcw'

Mark Dickinson added the comment: A reply to Ned from the person who introduced this bug in the first place (sorry, folks): [Ned] > 1. How to make core developers and patch contributors more aware of the > special requirements of multi-architecture builds? I guess I was already aware of this,

[issue7452] Invalid mnemonic 'fnstcw'

Ned Deily added the comment: I agree that adding the definitions of HAVE_GCC_ASM_FOR_X87 to pymacconfig.h solves the problem. [mini-rant on] This problem is another illustration of how easy it is to inadvertently introduce significant bugs in the OS X multi-architecture support, bugs which c

[issue7452] Invalid mnemonic 'fnstcw'

Mark Dickinson added the comment: Ronald: sorry, I wasn't clear. I only get that failure before your fix; afterwards, it's fine. -- ___ Python tracker ___ ___

[issue7452] Invalid mnemonic 'fnstcw'

Ned Deily added the comment: Ronald, it's a more complicated configure issue. I'm in the middle of pinning down the details. More shortly ... -- ___ Python tracker ___

[issue7452] Invalid mnemonic 'fnstcw'

Ronald Oussoren added the comment: Ned: which version of Python do you build? The issue was only in the trunk (2.7), the other branches were fine (although the code in 3.1 and 3.2 was suboptimal). BTW. The issue affected universal builds on all OSX versions. The trunk should be fine now as w

[issue7452] Invalid mnemonic 'fnstcw'

Mark Dickinson added the comment: Ned: maybe your pyconfig.h isn't defining HAVE_GCC_ASM_FOR_X87 in the first place, for some reason? I *do* get that error for trunk / 10.6 (with the 10.5 SDK; I don't have the 10.4 SDK installed): Mark-Dickinsons-MacBook-Pro:trunk dickinsm$ /usr/bin/gcc-4.

[issue7452] Invalid mnemonic 'fnstcw'

Ned Deily added the comment: "PPC (G3) machine rather than Intel (which shouldn't make a difference)" ... but did in this case. Perhaps it's too early in the morning yet but I don't see why that error doesn't show up for me when building trunk on an Intel machine under 10.6, i.e. this gives n

[issue7452] Invalid mnemonic 'fnstcw'

Sridhar Ratnakumar added the comment: > Do you get the same problem with py3k? Not in 3.1.1 at least. > Fixed in r76712 (trunk) That fixes the issue. Thanks! Let me know if you still need pyconfig.h. -- status: pending -> open ___ Python tracker

[issue7452] Invalid mnemonic 'fnstcw'

Ronald Oussoren added the comment: Fixed in r76712 (trunk), r76713 (3.2), r76714 (3.1). The python3 branches contained about half of the fix, I merged the trunk version into python3 anyway to keep all 3 branches in sync. The issue does not affect the 2.6 branch. -- resolution: -> fi

[issue7452] Invalid mnemonic 'fnstcw'

Ronald Oussoren added the comment: This is due to a block starting at '#ifdef HAVE_GCC_ASM_FOR_X87' in Python/pymath.c. A simple patch to pymacconfig.h fixes the issue, I'll commit it once I've fully tested the result. -- ___ Python tracker

[issue7452] Invalid mnemonic 'fnstcw'

Ronald Oussoren added the comment: Could you also post the generated pyconfig.h? -- ___ Python tracker ___ ___ Python-bugs-list mailin

[issue7452] Invalid mnemonic 'fnstcw'

Mark Dickinson added the comment: Do you get the same problem with py3k? -- ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue7452] Invalid mnemonic 'fnstcw'

Changes by Mark Dickinson : -- nosy: +mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue7452] Invalid mnemonic 'fnstcw'

Ned Deily added the comment: Works for me on 10.4.11 PPC (G3) machine rather than Intel (which shouldn't make a difference). But from your config.log, the gcc version is older than what I have on 10.4 (build 5250 vs build 5370). Suggest ensuring you have the most recent Xcode for 10.4 insta

[issue7452] Invalid mnemonic 'fnstcw'

Sridhar Ratnakumar added the comment: This error only occurs when I specify --enable-framework and --enable- universalsdk to ./configure. -- ___ Python tracker ___ __

[issue7452] Invalid mnemonic 'fnstcw'

New submission from Sridhar Ratnakumar : When trying to build 2.7a1 I ran into the following problem on MacOSX 10.4 (Tiger): $ ./configure --enable-framework --enable-universalsdk [...] $ make [...] gcc -c -arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk - fno-common -dynamic -DN