[Webkit-unassigned] [Bug 236829] Can't run WebKit (local build & nightly build) with Safari on M1 Max

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=236829

--- Comment #11 from Lingyun Cai <clyun2002 at 126.com> ---
> What do "which python" and "file `which python`" say on both? I wonder if
> different architectures of the python binary affect
> SafariForWebKitDevelpoment - although I couldn't reproduce any difference by
> forcing it with "arch" manually.

Here comes the difference. My M1 Max machine has Mach-O universal binary with 2 architectures while there is only x86_64 arch python binary on my M1. If I run the run-webkit-archive script with arch command, it succeeded in loading the frameworks in my working directory.
$ arch -x86_64 python run-webkit-archive

If forcing with arm64e as below, it failed in loading the frameworks.
$ arch -arm64e python run-webkit-archive

On my M1 machine:
$ python --version
Python 2.7.18
$ which python
/usr/local/bin/python
$ file `which python`
/usr/local/bin/python: Mach-O 64-bit executable x86_64

On my M1 Max machine:
$ python --version
Python 2.7.18
$ which python
/usr/bin/python
$ file `which python`
/usr/bin/python: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit executable x86_64] [arm64e:Mach-O 64-bit executable arm64e]
/usr/bin/python (for architecture x86_64):      Mach-O 64-bit executable x86_64
/usr/bin/python (for architecture arm64e):      Mach-O 64-bit executable arm64e

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220222/fdcaa036/attachment.htm>