strange problem building non-pure wheel for apple M1 arm64
Peter Pearson
pkpearson at nowhere.invalid
Tue Mar 8 11:00:59 EST 2022
On Mon, 7 Mar 2022 16:22:10 +0000, Robin Becker <robin at reportlab.com> wrote:
[snip]
>
> gcc -bundle -undefined dynamic_lookup -g -arch arm64
[snip]
> -L/usr/local/lib
> -L/usr/lib
> -L/Library/Frameworks/Python.framework/Versions/3.9/lib
> -lfreetype
[snip]
>
> ld: warning: ignoring file /usr/local/lib/libfreetype.dylib, building
> for macOS-arm64 but attempting to link with file
> built for macOS-x86_64
>
> The above message seems bizarre; everything is compiled for arm64, but
> gcc doesn't want to use an arm64 dylib.
>
> Can macos experts assist?
I am not at all expert in MacOS or any of the specifics of this
problem, but I think you want to try to prove that the libfreetype
invoked by "-lfreetype" is built for macOS-arm64 rather than for
macOS-x86-64.
--
To email me, substitute nowhere->runbox, invalid->com.
More information about the Python-list
mailing list