Bug Fails to compile on android arm 32

Anyone got it to compile any project on Android using Arm 32 bits?
My projects compile just fine for Arm 64 but they stopped compiling anything for 32 bits, which is still a huge user base.

When I try to compile it always gets stuck for about 20 minutes in Link_Android_arm32 Library/Bee/artifacts/Android/fy9m/libil2cpp.so

Then it times out with error:
Building Library\Bee\artifacts\Android\fy9m\libil2cpp.so failed with output:
C:/Java/android-ndk-r21d/toolchains/llvm/prebuilt/windows-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.9.x/../../../../arm-linux-androideabi/bin\ld.gold.exe: internal error in arm_branch_common, at /buildbot/src/android/binutils/toolchain/binutils/binutils-2.27/gold/arm.cc:4063
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
UnityEditor.GenericMenu:CatchMenu (object,string[],int)

 

We got the same error as you, when building on local machine.
But when building on server, error had extra description - "Out of memory" .
Increasing RAM from 14GB to 32 GB - solved the issue. But from observation, it seems like 17-18 Gb should be enough (still might depend on project size).
Nevertheless that looks like bug

 

Unfortunately now error is back, and even rebuilding previously successful changeset now fails

 

Yes, I can confirm this bug is back. In beta 9 you can't compile my project for arm32 again.

Can anyone submit a bug report? I can't. My project is so large that it fails to upload every single time. Tried for 3 days already. And I tried to trim it but I must touch something that stops the bug from happenning. It only happens with the full project.

 

Ok, I submitted it as 1363447 without any project since otherwise i can't even submit. And I added a request for QA to contact me with some other upload method. Btw, it's failing on b10 too.

thanks

 

nobody from QA contacts me...

 

nothing, still waiting. It's not like they need to check the project, i'm just waiting for them to tell me how to upload the project. Not sure why it's taking so long.

 

Got the same problem on the project and also could not submit it (probably it is too large), but managed to create and submit a smaller reproducible project. Case 1364218

 

I've submitted a project and basically got ignored. It's still not compiling on the oficial out of beta release. Stuck with 2021.1

 

Unity closed the case as it is an issue with android NDK and they cannot resolve it (https://issuetracker.unity3d.com/issues/android-build-fails-when-using-armv7-target-architecture).
As a workaround Unity devs suggested:
1. See if you can make the code used in this Unity project smaller. One option here is to use the new option discussed here: https://forum.unity.com/threads/il2cpp-build-time-improvements-seeking-feedback.1064135
2. It looks like this only happens when the C++ Compiler Configuration is set to "Master". You can instead use the "Release" configuration option.
We ended up usibg the 2nd option in our project

 

We are also getting this same issue after upgrading from version 2021.1.27f1 to 2021.2.7f1.
Out of memory on machine with 16GB RAM or stuck in Link_Android_arm32 on machine with 32GB RAM.
These workarounds are not suitable for us.

Is it possible that issue will be fixed in nearest releases (Android NDK will be updated)?
Or maybe there are other workarounds?

 

It's fixed on the updated Android NDK. All Unity has to do is use the newer NDK instead of an old one. Until then, we are stuck in 2021.1.27 too.

 

same issue here.
Unity should change the NDK version to something more up-to-date.

 

This drives me crazy. Impossible to compile IL2CPP for ARM64 on master mode.

 

Tried to use only the NDK from Unity 2022, and build with Unity 2021. didn't work.

 

those use the same NDK. They only upgraded the NDK on 2022.2 alpha versions. Until then, you are stuck with 2021.1.27 or not building on master mode. I don't understand why they decided to change the NDK in the middle of the 2021.1 versions and then don't upgrade it to fix what they broke.

 

I could compile my project setting C++ Compiler Configuration to Debug

 

If you don't set it to master it works. We know that. If you release using "debug", I feel sorry for your customers lol

 

This is a bug in this ticket, can you tell me how many NDK versions have fixed it?

 

I'm having the same problem with Unity 2021.3.6 with master c++ compiler configuration. It works fine with a release and debug. Which version of NDK helped with this issue?

 

The trick is to still use "Release", far as I'm aware...

Or try a more recent version of Unity:

 

2021.3.8f1 was released and this issue still happens. I wonder when will Unity solve this.

 

they are not solving it in the 2021 branches. I don't understand why they don't, but they don't. You need to move to 2022

 

That's a shame I agree. But I did some tests and posted a possible solution in another thread: https://forum.unity.com/threads/il2...-seeking-feedback.1064135/page-3#post-8411235

 

Wow thank you for this post, I was encountering the EXACT same problem and it was driving me crazy. Used your posted solution and it works again!
I had to change stripping to Medium (was Minimum) and removed a bunch of deprecated scripts to get it to compile again.