[issue7452] Invalid mnemonic 'fnstcw'
Ronald Oussoren
report at bugs.python.org
Wed Dec 9 22:38:15 CET 2009
Ronald Oussoren <ronaldoussoren at mac.com> 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 universal binaries and
Mac/BuildScript/build-installer.py is used to build the default binary
installer.
To build a universal binary framework:
../configure \
--enable-framework \ # Creates a framework
--enable-universalsdk # Create universal binary using 10.4 SDK
make
make install
The build can be tweaked using a number of options:
* Use an alternate SDK:
--enable-universalsdk=PATH
(I tend to use --enable-universalsdk=/ for my private builds,
the 10.4u SDK is used in the default installers to ensure that
users on 10.4 PPC can build universal extensions)
* Select architectures to include in the build:
--with-universal-archs=VALUE
* Pick an alternate framework name:
--with-framework-name=NAME
* Pick a different deployment target:
MACOSX_DEPLOYMENT_TARGET=X.Y
(Default is 10.3 for 32-bit builds and 10.5 for builds that include
a 64-bit architecture).
BTW. I agree that the current configure script sucks, it is very hard
to tweak it beyond adding simple feature tests. IIRC it has taken me
several Python releases to reliably run the feature detection tests
because some compiler flags didn't get exported correctly to the bits
of the configure script that runs the feature tests.
One way to improve on the script is to create a number of clearly
labeled sections, such as: compiler/platform setup, architecture tests
(SIZEOF_* detection, X86_FPU tests, ...), platform feature tests.
The architecture tests could then be prepended with a comment block
that explains how to deal with them for universal builds on OSX.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue7452>
_______________________________________
More information about the Python-bugs-list
mailing list