Search Issue Tracker
Fixed in 2022.1.X
Votes
1
Found in
2019.4.24f1
Issue ID
1327578
Regression
Yes
IL2CPP Linux build fails when building on CentOS 7
How to reproduce:
1. Create a new project
2. Open the "Build Settings" window by pressing Ctrl+Shift+B
3. Go into the player settings by pressing the "Player Settings..." button at the bottom left of the newly opened window
4. In the "Other Settings" section change the scripting backend to IL2CPP
5. Go back to the "Build Settings" window and build the project
6. Once the build is finished check the Console
Expected result: there is a message in the Console indicating that the build has been completed successfully
Actual result: the Console contains an error indicating that the build has failed
Reproducible with: 2019.4.24f1
Not reproducible with: 2020.3.4f1, 2021.1.3f1, 2021.2.0a14
Could not test with: 2018.4.34f1 (did not start)
Notes:
1. Reproducilbe on CentOS 7
2. Not reproducible on Ubuntu 18.04 and Windows 10
3. Console error: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /home/jeromy/il2cppcentostest/il2cppbuild/GameAssembly.so)
Comments (1)
-
TheoTowers
Jun 09, 2021 07:55
This appears to be happening again in 2021.2.0a19
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
- Crash on GUIManager::DoGUIEvent when focusing on the Game view window on a specific project
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
- Graphics State Collection warm-up does not work when using with Addressables Shaders
- "Baked Shadow Radius" field is visible but inactive when when the Shadow Type is set to "Hard Shadows" under the Light Component
Resolution Note (fix version 2022.1):
Fix included in following package versions:
com.unity.toolchain.linux-x86_64: 0.1.19-preview
com.unity.toolchain.macos-x86_64-linux-x86_64: 0.1.22-preview
com.unity.toolchain.win-x86_64-linux-x86_64: 0.1.21-preview
For this specific case (as reported), the first package is probably the one of interest.
Fixed in "Toolchain Linux x64" package version 0.1.19-preview