dae
commented
1 year ago Tried setting the deployment target to 11?
Open Cypher1 opened 1 year ago
dae
commented
1 year ago Tried setting the deployment target to 11?
Cypher1
commented
1 year ago Yes, sorry I didn't mention all the env vars above that mention 13.3 I've also tried with 11.0 (in multiple, though probably not all combinations).
It looks like the cc command doesn't pick up the MACOSX_DEPLOYMENT_TARGET properly and builds for (rather than just with) 13.3 (the newest SDK I have installed).
I haven't managed to install the Rust core libraries built with 11.0 though, so setting everything to 11.0 results in core missing.
Currently have checked out the pyoxidizer source to see if I can override the TARGET for cc there to make sure that is actually the problem.
dae
commented
1 year ago Tried clearing out your Rust compilation cache after setting the target to 11? I wonder if pyo3 declares it as something that should trigger a rebuild.
We use pyoxidizer in a slightly non-standard way so we can control the Rust program that is generated, and a deployment target of 11 works there, so there's a reasonable chance it would work in a standard build too.
Cypher1
commented
1 year ago Thanks. I tried that with the following attempts at cache clearing and
MACOSX_DEPLOYMENT_TARGET=11.0 \
SDKROOT=/Library/Developer/CommandLineTools/SDKs/MacOSX11.0.sdk \
STATIC_DEPS=true \
time pyoxidizer build --verbose 2>&1 | tee logfileI'm using static deps because otherwise I get a bunch of errors about xslt...
Cache clearing:
./build directory~/.cargo/target.Any other caches around the place?
I'm wondering if it's actually the pyoxidizer built with pyoxide. I'll try building pyoxidizer from source again with the MACOSX_DEPLOYMENT_TARGET=11.0
dae
commented
1 year ago Not sure I'm afraid. In case it's helpful, this is how we build: https://github.com/ankitects/anki/blob/main/build/runner/src/bundle/binary.rs builds https://github.com/ankitects/anki/tree/main/qt/bundle. It uses a slightly patched version of PyOxidizer for #466.
Cypher1
commented
1 year ago Darn, still trying things. Built pyoxidizer from scratch targeting 11.0.
= note: ld: in /private/var/folders/j8/17r7x0c91_b50dh7l1jst1ph0000gn/T/pyoxidizerJvWGUn/build/target/aarch64-apple-darwin/debug/deps/libpyo3_ffi-0c5d1fc6c366c825.rlib(libpython.127.o), archive member 'libpython.127.o' with length 1907936 is not mach-o or llvm bitcode file '/private/var/folders/j8/17r7x0c91_b50dh7l1jst1ph0000gn/T/pyoxidizerJvWGUn/build/target/aarch64-apple-darwin/debug/deps/libpyo3_ffi-0c5d1fc6c366c825.rlib' for architecture arm64I'll try to learn from your patch. (Much appreciated)
Cypher1
commented
1 year ago logfile.txt Progress via building pyoxidizer for 11.0 and the project for 13.3
Not sure what the pip error is but I'm hoping it's just relative paths.
It seems there's some version mismatch between the SDK that I have (13.3) and the one that rust is linking to (11.0).
Full command for
ccAdded full logfile as an attachment. logfile.txt
I've tried a few combinations of the following env variables with no success (and even managed to get rustc to fail to find
corein some instances.Is my setup misconfigured? Am I holding it wrong?
Thanks in advance