-
Notifications
You must be signed in to change notification settings - Fork 704
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
out of range immediate fixup value for ndk r18b and arm #798
Comments
I've cloned cc, renamed |
I hit this same issue. Can you provide your cloned cc? How do that? |
My cloned cc is here, branch marm: |
@chengchangwu and @mamcx do you have issues if you you clang too? |
@pietro Yes, my config is with clang:
for example... |
Please try removing the mention of poly1305-armv4.pl from build.rs and report back what error(s) you get. In particular, do you get "error: out of range immediate fixup value" from any other files? If so, please post all of them. In particular, if the problem is only in the function |
Also, does this happen when you use the |
The latest stable version of the NDK is r19b. So, let's see if this happens with r19b. |
openssl/openssl#7878 (comment) indicates that NDK r19 might have a similar issue compiling the AES module but nobody has said anything about r19 and the poly1305 module. If poly1305-armv4 works in R19 then I probably won't change poly1305-armv4. If the AES module doesn't work in R19 then I will consider replacing the AES module, depending on where the fixup error is. Thanks for suggesting the workaround of using |
Hi everyone, I was experiencing this same problem. I upgraded to NDK R20 and also noticed that its no longer required to make a standalone toolchain if using NDK R19 and later according to: So I went ahead and tried to build aarch64, armv7a, and i686 android using the NDK software that was installed via android-studio sdkmanager. Which worked when building with the following environment variables set (note that my android-studio software is installed in $HOME/Android/ in the following)
and this now builds without error. |
I think it is OK to make the minimum NDK version R20. Let me know if there is any objection to this. Also, it would be great to have a PR to use NDK R20 in CI. |
I didn't experience this using NDK 20 with either |
the original bug report had "arm-linux-androideabi-gcc" as the C compiler. Another user privately reported similar trouble using the GCC-based toolchain. I think the solution is to use clang. |
I am using ndk 20b and armv7a-linux-androideabi28-clang, and got the error as in the first comment. I need to remove 'poly1305-armv4.pl' to get it to build passed. |
Remove per suggestion in issue briansmith#798.
Error:
The compilation only fails with arm, not with x86 or aarch64.
I have found some reports by other projects which may be useful:
If I want to use -marm instead of -mthumb to workaround this problem, where in the code should I look at?
The text was updated successfully, but these errors were encountered: