[MacPorts] #66129: Pythons are broken for +universal, even on Intel with Clang
MacPorts
noreply at macports.org
Tue Nov 1 07:00:00 UTC 2022
#66129: Pythons are broken for +universal, even on Intel with Clang
--------------------------+-------------------------------------------
Reporter: barracuda156 | Owner: jmroot
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.8.0
Keywords: | Port: python310, python39, python38
--------------------------+-------------------------------------------
I have been long saying that Pythons are broken for `+universal` on PPC,
and that been ignored, because ''no one cares''. Well, it is also broken
on Intel:
{{{
clang: error: clang frontend command failed with exit code 70 (use -v to
see invocation)
Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn)
Target: i386-apple-darwin12.6.0
Thread model: posix
clang: note: diagnostic msg: PLEASE submit a bug report to
http://developer.apple.com/bugreporter/ and include the crash backtrace,
preprocessed source, and associated run script.
clang: note: diagnostic msg: Error generating preprocessed source(s) -
cannot generate preprocessed source with multiple -arch options.
make: *** [Modules/signalmodule.o] Error 70
make: *** Waiting for unfinished jobs....
}}}
I actually have fixed all Pythons locally to build as universal. Tested
for ppc+ppc64 on Leopard, but presumably gonna work on any system for
Intel.
I wanna avoid a situation when my PR is just closed (instead of advising
me a better way to do it, where needed), like last time with a fix for
Python LTO on PPC.
If there is an interest in having this fixed, I can open a PR – and
request for help to check it (it is not the case where I am sure
everything works correctly and optimally – but at least it does work,
unlike existing universal).
--
Ticket URL: <https://trac.macports.org/ticket/66129>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list