The “R_ARM_TLS_LE32 relocation not permitted in shared object” error typically occurs when attempting to use the R_ARM_TLS_LE32 relocation type in a shared object file on an ARM-based architecture.
The TLS (Thread Local Storage) is used for implementing thread-local variables, which have different instances per thread. However, some ARM architectures do not support the R_ARM_TLS_LE32 relocation type in shared objects. This error indicates that you are trying to use this unsupported relocation type.
To resolve this issue, you can consider the following options:
Check your toolchain and ensure that it supports TLS relocations for shared objects on your target architecture. If necessary, update your toolchain or switch to a different one that provides proper support.
If you don’t specifically require TLS functionality in your shared object, you can disable it by removing or modifying any TLS-related code or declarations.
If TLS is essential for your application and cannot be disabled, you may need to find an alternative solution or workaround specific to your situation and target platform.
Please note that the exact steps to resolve this issue may vary depending on your specific development environment and requirements.
内容由零声教学AI助手提供，问题来源于学员提问
![const dataInfo= dialogData.data[i];const htmlContent =](https://linuxcpp.0voice.com/zb_users/upload/2023/05/202305162217459776743.png)
![varif(dialogData.success){(let i=0;i< dialogData.data.length; i++){l/ for
TTself.customerName.setValue(dialogData.datalil.name)A3self.customerCodes.setValue(dialogData.data[i].customerId)
for(let i=0;i](https://linuxcpp.0voice.com/zb_users/upload/2023/05/202305162216215163775.png)
