arm-none-linux-gnueabi vs arm-linux – EABI vs Non-EABI

最新推荐文章于 2022-04-23 19:34:13 发布

yhNENG

最新推荐文章于 2022-04-23 19:34:13 发布

阅读量1k

点赞数 1

分类专栏： vivi 文章标签： application interface kill linux file

vivi 专栏收录该内容

16 篇文章

订阅专栏

本文探讨了在使用不同编译器（如codesourcery、ADS等）创建的EABI和非EABI二进制文件之间存在的不兼容性问题。详细介绍了如何通过下载非EABI的arm-linux目标工具链解决Linux内核加载使用EABI工具链构建的根文件系统时出现的Kernel panic问题。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

EABI is the new Application Binary Interface (ABI) specification for the ARM Architecture introduced in 2005. It aims to provide interoperability between binaries compiled by various compilers like codesourcery, ADS, RVCT, RVDS, etc. Which previous non-EABI binaries couldn’t provide. Thus, It is possible to link libraries created using different compilers with EABI support but old ABI libraries lacked that compatibility. This caused a lot of trouble to me recently. I compiled the linux kernel with EABI turned off. Then I compiled busybox and other libraries using arm-none-linux-gnueabi target as dynamically shared libraries. The kernel won’t load the rootfs built using EABI toolchain. It used to print, Kernel panic – not syncing: Attempted to kill init! I downloaded another toolchain(arm-linux target this time) and compiled the rootfs using it. This time, kernel had no trouble loading the file system. As I searched further, I learned that EABI and non-EABI are not inter-operable and hence the mess. I also learned that all the toolchain supplied by codesourcery since 2005 are EABI based. The arm-linux toolchain I downloaded recently(which is non-EABI) is not from codesourcery.