[MacPorts] #24802: set python module -arch flags when running setup.py
#24802: set python module -arch flags when running setup.py ------------------------------+--------------------------------------------- Reporter: jmr@… | Owner: blb@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: python26 ------------------------------+--------------------------------------------- It's possible to pass compiler flags to setup.py in the environment. These are added to what is listed in config/Makefile. So we should strip the -arch flags out of there, and add them in the portgroup, which would allow us to build non-universal modules against a universal python. -- Ticket URL: <http://trac.macports.org/ticket/24802> MacPorts <http://www.macports.org/> Ports system for Mac OS
#24802: set python module -arch flags when running setup.py ------------------------------+--------------------------------------------- Reporter: jmr@… | Owner: blb@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: python26 ------------------------------+--------------------------------------------- Comment(by blb@…): How many modules should we test before considering this safe to add? I've tested a couple, both with and without universal (py26-libxml2 and py26-numpy, without atlas or gcc43) and things seem fine so far. Also, should this go into 2.7 and 3.1 as well? -- Ticket URL: <http://trac.macports.org/ticket/24802#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#24802: set python module -arch flags when running setup.py ------------------------------+--------------------------------------------- Reporter: jmr@… | Owner: blb@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: python26 ------------------------------+--------------------------------------------- Comment(by jmr@…): Well, I figure this probably gets it right a lot more often than the current approach. One more thing needed is to give the modules a universal variant by default, which I've done in the updated patch by replacing 'use_configure no' with 'configure {}' (they can use supported_archs or 'universal_variant no' to turn it off). And yeah, this is equally applicable to the newer versions AFAIK. -- Ticket URL: <http://trac.macports.org/ticket/24802#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#24802: set python module -arch flags when running setup.py ------------------------------+--------------------------------------------- Reporter: jmr@… | Owner: blb@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: python26 python27 python31 ------------------------------+--------------------------------------------- Changes (by blb@…): * cc: jwa@…, erickt@… (added) * port: python26 => python26 python27 python31 Comment: Cc'd python27 and python31 maintainers. python26 (and portgroup) updated in r67722. Now we'll see which modules have odd build systems... -- Ticket URL: <http://trac.macports.org/ticket/24802#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#24802: set python module -arch flags when running setup.py ------------------------------+--------------------------------------------- Reporter: jmr@… | Owner: blb@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: python26 python27 python31 ------------------------------+--------------------------------------------- Comment(by ryandesign@…): r67722 causes python26 portgroup ports like mercurial to fail on MacPorts < 1.9.0 because it uses the configure.ld_archflags variable which is not available until MacPorts 1.9.0. See [http://lists.macosforge.org/pipermail /macports-users/2010-May/020151.html this mailing list report]. -- Ticket URL: <http://trac.macports.org/ticket/24802#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS
#24802: set python module -arch flags when running setup.py ------------------------------+--------------------------------------------- Reporter: jmr@… | Owner: blb@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: python26 python27 python31 ------------------------------+--------------------------------------------- Comment(by jmr@…): Put in a fix/hack for python ports that set use_configure yes in r67762. -- Ticket URL: <http://trac.macports.org/ticket/24802#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS
#24802: set python module -arch flags when running setup.py ------------------------------+--------------------------------------------- Reporter: jmr@… | Owner: blb@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: python26 python27 python31 ------------------------------+--------------------------------------------- Comment(by jmr@…): I'll apply this to python27 and python31 shortly unless the maintainers object. -- Ticket URL: <http://trac.macports.org/ticket/24802#comment:7> MacPorts <http://www.macports.org/> Ports system for Mac OS
#24802: set python module -arch flags when running setup.py -----------------------------------------+---------------------------------- Reporter: jmr@… | Owner: blb@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: python26 python27 python31 | -----------------------------------------+---------------------------------- Changes (by jmr@…): * status: new => closed * resolution: => fixed Comment: Applied in r68551. -- Ticket URL: <http://trac.macports.org/ticket/24802#comment:8> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts