-
Notifications
You must be signed in to change notification settings - Fork 410
Duplicate symbol pthread_atfork
when compiling Android release
#1221
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
Comments
Going to ask the same question here as I asked in #1222, what version of rust is this might be a wrong assumption done for the new ndk also, did this recently break (e.g has it worked before)? We did a fresh build of the images on |
So no chance an stable either. |
It is not a very complex program, compiling does not take longer than 3 minutes for me. Docker pull takes way longer.
|
sorry, the I'll remove the label :) |
Ok, no worries, at least now you have a little more info 😉 |
Removing these lines solves the problem: https://github.com/MarcelCoding/zia/blob/main/Cargo.toml#L8-L17 I'll further investigate which property exact is the problem. |
Removing jmalloc MarcelCoding/zia@ |
Seems to work with the changes. |
It seems to be related to this issue, and it has been fixed. |
Checklist
Describe your issue
Building https://github.com/MarcelCoding/zia for target
aarch64-linux-android
fails to link. The linker fails because of "duplicate symbolpthread_atfork
".What target(s) are you cross-compiling for?
aarch64-linux-android
Which operating system is the host (e.g computer cross is on) running?
What architecture is the host?
What container engine is cross using?
cross version
cross 0.2.5 99b8069 2023-02-12
Example
Additional information / notes
Same build is fine for e.g
aarch64-unknown-linux-gnu
. And it builds fine foraarch64-linux-android
if you do the debug build, and not the release build.Do you know any solution for this?
It is very strange, that only the release version is affected....
It does not matter, if I do it in GH actions, or locally, using the same commands. Same error.
The text was updated successfully, but these errors were encountered: