Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.41f1
2022.3.39f1
6000.0.12f1
Issue ID
UUM-76527
Regression
No
[Android] Build fails due to "stderr not found..." error when building for Android with C++ static libs and using IL2CPP Scripting Backend
How to reproduce:
1. Open the attached “IN-80821.zip” project
2. Open the Build Settings window (File → Build Settings…)
3. Change the Build Target to Android
4. Build the Project
Expected result: The Build is successful
Actual result: The Build fails and “ld.lld: error: undefined symbol: stderr” error is thrown
Reproducible with: 2021.3.41f1, 2022.3.39f1, 6000.0.12f1
Reproducible on: macOS M1 Max, macOS 14.15 (Intel)
Not reproducible on: No other environment tested
Notes:
- The issue is not reproducible with Mono Scripting Backend
- The issue is not reproducible when building for Standalone
- The reporter noted that the issue is not supposed to reproduce as “stderr” is a standard library
- Full error message:
”Building Library/Bee/artifacts/Android/iz17e/libil2cpp.so failed with output:
ld.lld: error: undefined symbol: test_c
>>> referenced by Assembly-CSharp.cpp:227 (Library/Bee/artifacts/Android/il2cppOutput/cpp/Assembly-CSharp.cpp:227)
>>> Library/Bee/artifacts/Android/iz17e/lk81nll58e8a.o:(test_test_c_m83DA76F808553D2DC88A7ECE5FB0AA0AF1EA45FE)
>>> referenced by Assembly-CSharp.cpp:227 (Library/Bee/artifacts/Android/il2cppOutput/cpp/Assembly-CSharp.cpp:227)
>>> Library/Bee/artifacts/Android/iz17e/lk81nll58e8a.o:(test_Start_mEC610EE12F006B73DD8DBE742E8660D39BFF518F)
clang++: [0;1;31merror: [0m[1mlinker command failed with exit code 1 (use -v to see invocation)[0m
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&) (at /Users/bokken/build/output/unity/unity/Modules/IMGUI/GUIUtility.cs:219)”
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
One thing to check with static libraries is that Unity is built with -fno-exceptions -fno-rtti flags. If libraries don’t have these, that can cause compatibility issues.