-
-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hundreds of warnings when linking core main
branch
#2104
Comments
this issue is fixed somehow by 1.136.2, together with deltachat/deltachat-android#2972 :) |
main
branch
the warnings are back again on ~current core master - while using deltachat/deltachat-core-rust#5387 was fine - sth. has changed in between, i cannot make sense of that @link2xt these are warnings only - but do you have any clue what could cause that? so it is easier to get rid of them :) EDIT: i just updated macos to "Sonoma 14.4.1" and Xcode to 15.3 - still the same warnings. will try if rust 1.77 changes anything. EDIT: no change in my understanding,, by some core changes, things are suddenly build for 17.2 instead of 12.0 - and that could also be reverted - the issue was there for 1.136.1 and disappeared with 1.136.2 and https://stackoverflow.com/questions/50703177/cannot-compile-rust-code-on-macos-10-12-object-file-was-built-for-newer-osx-ver (via search "rust lipo Object file was built for newer version than being linked") points to some possible environment vars - EDIT: tried adding "export IPHONEOS_DEPLOYMENT_TARGET=8.0" atop of "Build Phases / Run Script" - no change 💫 maybe i wait just for another core update that let the warnings magically disappear as from 1.136.1 to 1.136.2 🪄🎩 |
Between 1.136.1 and 1.136.2 we downgraded |
Breaking change is probably this one: rust-lang/cc-rs#848 |
thanks a lot for the info, this js very helpful! i will have a closer look at the environment vars then |
Just grepping over |
I did a PR #2139 with a quick |
sorry, the "8.0" was a copy+paste error, i meant "export IPHONEOS_DEPLOYMENT_TARGET=12.0" still, good to see in #2139 that things are 12.0 everywhere - @zeitschlag set that to 12.0 at #2034 to fix other issues. it seems Xcode is really picky to have deployment target the same everywhere, i will keep investigating (and still try your PR, who knows :) |
I am trying to run the build core commit d39c8a3a19c29c31af5db208524ab1a749b309b6 on macOS with just
It fails with this output:
This is probably due to running in a Nix shell, will try to run without it as it wraps CC probably. |
@r10s |
This looks like a problem is cargo-lipo, it explicitly removes |
comping/linking core 1.136.1 results in lots of warnings as
full log: https://gist.github.com/r10s/5beceb77824ce72566883a0fadc198ce
rust-toolchain: 1.73.0 (unchanged)
build-environment: macOS Sonoma 14.3.1
just ftr for now, i did not try to make sense of it.
apart from the updated submodule nothing has changed. i also double checked to build core 1.135 in the same environment - no error or warning
maybe some xcode option need to be tweaked, but interesting that it does not happen for 1.135
maybe somehow releated: deltachat/deltachat-android#2972
The text was updated successfully, but these errors were encountered: