arm-linux/elf/eabi交叉编译器

最新推荐文章于 2024-06-25 18:17:38 发布
转载 最新推荐文章于 2024-06-25 18:17:38 发布 · 2.9k 阅读 · 1
文章标签：

#编译器 #嵌入式 #linux

本文介绍了ARM架构下三种主要的交叉编译器类型：arm-linux-、arm-elf- 和 arm-eabi。详细解释了它们的应用场景及特点，特别是arm-eabi对浮点运算的支持及其对硬件的影响。

原文：http://blog.chinaunix.net/uid-25871104-id-2950902.html

arm的交叉编译器有三种类型(命名方式)：arm-linux-, arm-elf-, arm-eabi

arm-linux一般用于编译linux程序，使用glibc库，arm-linux-elf用于编译uclinux或其他程序，使用嵌入式库，如uclib或newlib等。

arm-eabi是符合eabi规范的交叉编译器。关于EABI，可以参考另一篇博文。简单的说，EABI定义了一系列规范，如过程调用规范aacp，系统调用规范等。
arm-eabi可以使用各种不同的lib。
arm-eabi相比较前两者，最大的特点是，它支持FPA(Floating Pointer Accelrator)，可以有效的提高浮点运算速度。但是对于没有FPA单元的硬件，使用arm-eabi编译的程序运行会更慢，因为对FPA的指令会产生未知指令的异常。



另外还可以参考：

http://blog.youkuaiyun.com/wfing/article/details/5818227

Cannot run program‘null\code【鸿蒙报错已解决】
一键难忘的博客
05-02 436
Cannot run program‘null\code【鸿蒙报错已解决】最近遇到了这个问题，看到网上也有人在询问这个问题，实操了很多网上的解决方案发现并不能解决这个Bug，所以我在解决这个问题后，总结了自己和其他人的解决经验，进行了整理，写了一本解决【Cannot run program‘null\code】这个问题的bug文章，希望可以帮助到大家。 解决问题的全部过程记录在本篇文章中，包括原因分析、解决方案等，按照本文的解决方案应当可以解决这个报错。
新版本ARM交叉编译器官网下载地址(arm-none-eabi、arm-none-linux-gnueabihf、aarch64-none-elf、aarch64-none-linux-gnu)
04-27 1万+
交叉编译器官网下载地址：https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-a/downloads
Android Studio 加载第三方库
rensichao的博客
06-25 1585
3.3 如果路径中使用${CMAKE_ANDROID_ARCH_ABI}，则ndk需要含有四种架构，且libs目录下也要有四种对应的库。总结：以上只是会为了调试结果而写的记录，没有仔细分析原理。我是按照上面博主的分享尝试的，现记录一下自己遇到的问题。
已经编译好so库的 FFMPEG0.8.3
04-30
根据网上教程在ubuntu下通过ndk-r6b编译ffmpeg0.8.3版本，包含ffmpeg的源代码，已经生成的动态库libffmpeg.so 方便大家学习及使用。
arm-linux/elf/eabi 交叉编译器
沉淀
07-22 1938
arm的交叉编译器有三种类型(命名方式)：arm-linux-, arm-elf-, arm-eabi- arm-linux： 一般用于编译linux程序，使用glibc库 arm-linux-elf： 用于编译uclinux或其他程序，使用嵌入式库，如uclib或newlib等。 arm-eabi： 是符合eabi规范的交叉
arm-linux eabi 交叉工具链编译笔记
sdutyl的专栏
01-01 1287
首先感谢网上很多前辈的文章，可以少走些弯路。主要参照了下边的文章     http://hi.baidu.com/fuchenyipie/item/cfb1b2143a455f4ae65e06a6     http://hi.baidu.com/busybox/item/3278ef1c2bfb32fa65eabff4       http://book.51cto.com/art
hqyj@ubuntu:~$ dpkg -L gcc-arm-linux-gnueabihf 2>/dev/null | grep bin/arm-linux-gnueabihf-gcc hqyj@ubuntu:~$ hqyj@ubuntu:~$ find /usr /opt ~/ -name "arm-linux-gnueabihf-gcc" 2>/dev/null hqyj@ubuntu:~$ dpkg -L gcc-arm-none-eabi 2>/dev/null | grep bin/arm-none-eabi-gcc hqyj@ubuntu:~$ dpkg -L gcc-arm-none-eabi 2>/dev/null | grep bin/arm-none-eabi-gcc hqyj@ubuntu:~$ find /usr /opt ~/ -name "arm-none-eabi-gcc" 2>/dev/null /opt/st/stm32mp1/3.1-openstlinux-5.4-dunfell-mp1-20-06-24/sysroots/x86_64-ostl_sdk-linux/usr/share/gcc-arm-none-eabi/bin/arm-none-eabi-gcc /opt/st/fsmp1a/3.1-snapshot/sysroots/x86_64-ostl_sdk-linux/usr/share/gcc-arm-none-eabi/bin/arm-none-eabi-gcc hqyj@ubuntu:~$ dpkg -L gcc-arm-none-eabi 2>/dev/null | grep bin/arm-none-eabi-gcc hqyj@ubuntu:~$ find /usr /opt ~/ -name "arm-none-eabi-gcc" 2>/dev/null /opt/st/stm32mp1/3.1-openstlinux-5.4-dunfell-mp1-20-06-24/sysroots/x86_64-ostl_sdk-linux/usr/share/gcc-arm-none-eabi/bin/arm-none-eabi-gcc /opt/st/fsmp1a/3.1-snapshot/sysroots/x86_64-ostl_sdk-linux/usr/share/gcc-arm-none-eabi/bin/arm-none-eabi-gcc hqyj@ubuntu:~$
07-18
另外，在用户下载目录中也有一个旧版本（gcc-4.6.4）的交叉编译器，其中包含arm-none-linux-gnueabi-gcc，但不是arm-none-eabi-gcc。 最后使用which命令也没有找到，说明这些路径可能不在环境变量PATH中。 根据...
LDFLAGS = -L/home/lkk/Desktop/gcc-arm-none-eabi-2020/arm-none-eabi/lib LDFLAGS+= -L/home/lkk/Desktop/gcc-arm-none-eabi-2020/lib/gcc/arm-none-eabi/10.2.1这两个是干啥的？
最新发布
12-08
arm-none-eabi-gcc main.o -o output.elf $(LDFLAGS) -lc -lgcc 这样，链接器会在指定的两个路径中查找libc.a和libgcc.a。 §§相关问题§§ 1. 为什么需要为arm-none-eabi工具链分别指定多个库搜索路径？ 2. 在...
arm-none-linux-gnueabi-gcc-4.8.3
07-24
arm-none-linux-gnueabi-gcc是 Codesourcery 公司（目前已经被Mentor收购）基于GCC推出的的ARM交叉编译工具。可用于交叉编译ARM系统中所有环节的代码，包括裸机程序、u-boot、Linux kernel、filesystem和App应用程序...
“PREFIX = arm-none-eabi- CC = $(PREFIX)gcc STM32_Per_Src_Path = Libraries/STM32F10x_StdPeriph_Driver/src SOURCES = User/main.c SOURCES += User/stm32f10x_it.c #SOURCES += Libraries/CMSIS/core_cm3.c SOURCES += Libraries/CMSIS/system_stm32f10x.c SOURCES += $(STM32_Per_Src_Path)/misc.c SOURCES += $(STM32_Per_Src_Path)/stm32f10x_rcc.c SOURCES += $(STM32_Per_Src_Path)/stm32f10x_gpio.c ASM_SOURCES = Libraries/CMSIS/start.S OBJS = $(SOURCES:.c=.o) $(ASM_SOURCES:.S=.o) TARGET = build/stm32f103_project MCU=cortex-m3 CFLAGS = -mcpu=$(MCU) -mthumb CFLAGS += -Wall -Wextra -Wpedantic #CFLAGS += -Wmissing-prototypes -Wstrict-prototypes CFLAGS += -DSTM32F10X_MD CFLAGS += -DUSE_STDPERIPH_DRIVER #CFLAGS += --specs=nano.specs CFLAGS += --specs=nosys.specs INCLUDE = -IUser INCLUDE += -ILibraries\STM32F10x_StdPeriph_Driver\inc INCLUDE += -ILibraries\CMSIS INCLUDE += -Iinterrupt INCLUDE += -IAPP LDSCRIPT = STM32F103C8_FLASH.ld LDFLAGS = -mcpu=$(MCU) -mthumb #LDFLAGS += --specs=nano.specs LDFLAGS += --specs=nosys.specs LDFLAGS += -T$(LDSCRIPT) -Wl,--gc-sections LDFLAGS += -Wl,--print-memory-usage LDFLAGS += -Wl,-Map=Build/project.map all : $(TARGET).elf $(TARGET).bin $(TARGET).hex $(TARGET).elf: $(OBJS) @echo Linking... $(CC) $(LDFLAGS) -o $@ $^ @echo Size info: $(SIZE) $@ %.o: %.c @echo Compiling $<... $(CC) $(CFLAGS) $(INCLUDE) -c -o $@ $< %.o: %.s @echo Assembling $<... $(CC) $(CFLAGS) -c -o $@ $< $(TARGET).bin: $(TARGET).elf $(OBJCOPY) -O binary $< $@ $(TARGET).hex: $(TARGET).elf $(OBJCOPY) -O ihex $< $@ clean: rm -rf Build find . -name "*.o" -type f -delete find . -name "*.d" -type f -delete flash: $(TARGET).elf openocd -f interface/stlink.cfg -f target/stm32f1x.cfg \ -c "program $< verify reset exit" clean: -del /q $(subst /,\,$(OBJS)) 2>nul -del /q $(TARGET).elf $(TARGET).bin $(TARGET).hex $(TARGET).map 2>nul flash: $(TARGET).elf openocd -f interface/stlink.cfg -f target/stm32f1x.cfg -c "program $< verify reset exit" .PHONY: all clean flash”“PS C:\Users\13336\Desktop\test\vscode_stm32\model_02> mingw32-make all makefile:87: warning: overriding recipe for target 'flash' makefile:79: warning: ignoring old recipe for target 'flash' Compiling User/main.c... arm-none-eabi-gcc -mcpu=cortex-m3 -mthumb -Wall -Wextra -Wpedantic -DSTM32F10X_MD -DUSE_STDPERIPH_DRIVER --specs=nosys.specs -IUser -ILibraries\STM32F10x_StdPeriph_Driver\inc -ILibraries\CMSIS -Iinterrupt -IAPP -c -o User/main.o User/main.c Linking... arm-none-eabi-gcc -mcpu=cortex-m3 -mthumb --specs=nosys.specs -TSTM32F103C8_FLASH.ld -Wl,--gc-sections -Wl,--print-memory-usage -Wl,-Map=Build/project.map -o build/stm32f103_project.elf User/main.o User/stm32f10x_it.o Libraries/CMSIS/system_stm32f10x.o Libraries/STM32F10x_StdPeriph_Driver/src/misc.o Libraries/STM32F10x_StdPeriph_Driver/src/stm32f10x_rcc.o Libraries/STM32F10x_StdPeriph_Driver/src/stm32f10x_gpio.o Libraries/CMSIS/start.o C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/bin/ld.exe: C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/lib/thumb/v7-m/nofp\libc.a(libc_a-closer.o): in function `_close_r': closer.c:(.text._close_r+0xc): warning: _close is not implemented and will always fail C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/bin/ld.exe: C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/lib/thumb/v7-m/nofp\libc.a(libc_a-closer.o): note: the message above does not take linker garbage collection into account C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/bin/ld.exe: C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/lib/thumb/v7-m/nofp\libc.a(libc_a-lseekr.o): in function `_lseek_r': lseekr.c:(.text._lseek_r+0x14): warning: _lseek is not implemented and will always fail C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/bin/ld.exe: C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/lib/thumb/v7-m/nofp\libc.a(libc_a-lseekr.o): note: the message above does not take linker garbage collection into account C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/bin/ld.exe: C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/lib/thumb/v7-m/nofp\libc.a(libc_a-readr.o): in function `_read_r': readr.c:(.text._read_r+0x14): warning: _read is not implemented and will always fail C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/bin/ld.exe: C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/lib/thumb/v7-m/nofp\libc.a(libc_a-readr.o): note: the message above does not take linker garbage collection into account C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/bin/ld.exe: C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/lib/thumb/v7-m/nofp\libc.a(libc_a-writer.o): in function `_write_r': writer.c:(.text._write_r+0x14): warning: _write is not implemented and will always fail C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/bin/ld.exe: C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/lib/thumb/v7-m/nofp\libc.a(libc_a-writer.o): note: the message above does not take linker garbage collection into account C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/bin/ld.exe: warning: build/stm32f103_project.elf has a LOAD segment with RWX permissions C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/bin/ld.exe: User/main.o: in function `main': main.c:(.text+0x4): undefined reference to `SetSysClock' C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/bin/ld.exe: (SetSysClock): Unknown destination type (ARM/Thumb) in User/main.o main.c:(.text+0x4): dangerous relocation: unsupported relocation C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/bin/ld.exe: main.c:(.text+0x8): undefined reference to `LED_Init' C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/bin/ld.exe: (LED_Init): Unknown destination type (ARM/Thumb) in User/main.o main.c:(.text+0x8): dangerous relocation: unsupported relocation C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/bin/ld.exe: main.c:(.text+0xc): undefined reference to `LED_On' C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/bin/ld.exe: (LED_On): Unknown destination type (ARM/Thumb) in User/main.o main.c:(.text+0xc): dangerous relocation: unsupported relocation C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/bin/ld.exe: main.c:(.text+0x14): undefined reference to `Delay_ms' C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/bin/ld.exe: (Delay_ms): Unknown destination type (ARM/Thumb) in User/main.o main.c:(.text+0x14): dangerous relocation: unsupported relocation C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/bin/ld.exe: main.c:(.text+0x18): undefined reference to `LED_Off' C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/bin/ld.exe: (LED_Off): Unknown destination type (ARM/Thumb) in User/main.o main.c:(.text+0x18): dangerous relocation: unsupported relocation C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/bin/ld.exe: main.c:(.text+0x20): undefined reference to `Delay_ms' C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/bin/ld.exe: (Delay_ms): Unknown destination type (ARM/Thumb) in User/main.o main.c:(.text+0x20): dangerous relocation: unsupported relocation Memory region Used Size Region Size %age Used FLASH: 1540 B 64 KB 2.35% RAM: 1984 B 20 KB 9.69% collect2.exe: error: ld returned 1 exit status mingw32-make: *** [makefile:55: build/stm32f103_project.elf] Error 1 PS C:\Users\13336\Desktop\test\vscode_stm32\model_02>”这报错是什么问题
09-29
C:/Users/13336/Desktop/test/arm-gnu-toolchain-14.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/bin/ld.exe: C:/Users/13336/Desktop/test/arm-gnu-...
arm-elf/arm-eabi/arm-none-eabi
yazhouren的专栏
06-02 867
eabi是arm新的二进制文件接口的标准，elf是二进制目标文件的格式，而名称为arm-elf的编译器一般是老的OABI接口，裸奔程序到影响不大，在嵌入式linux中，要注意系统的接口，是老的oabi还是eabi，新的内核一般是eabi接口，但编译内核时会有兼用oabi接口的选项，默认是没选择的，需要的话编译时需要手动选上 那个none指的是没有操作系统的意思，glibc里面跟os有关的内容删掉
arm交叉编译器gnueabi、none-eabi、arm-eabi、gnueabihf、gnueabi区别以及使用arm-none-eabi-工具连编译zephyr sdk.
tugouxp的专栏
02-17 2597
命名规则交叉编译工具链的命名规则为：arch [-vendor] [-os] [-(gnu)eabi]arch - 体系架构，如ARM，MIPS vendor - 工具链提供商 os - 目标操作系统 eabi - 嵌入式应用二进制接口（Embedded Application Binary Interface） 根据对操作系统的支持与否，ARM GCC可分为支持和不支持操作系统，如arm-
安装arm-elf-gcc
沧海浮云的世界 一步一个脚印
04-04 5049
从www.uclinux.org下载arm-elf-tools ,载到了arm-elf-tools-20030314.sh , 看网上有更新的版本，但没有看到。运行./arm-elf-tools-20030314.sh    注：用Root权限运行出现错误：tail: 无法打开“+43” 读取数据: 没有那个文件或目录。gunzip: stdin: not in gzip format
arm-linux-gcc-4.3.2 with eabi,关于arm-eabi-gcc和交叉编译
weixin_29721821的博客
05-13 352
我有一个需要移植到的复杂的开源库Android NDK。首先，我需要配置(./configure)。我明白：我必须用/ home / user / android-ndk / build / prebuilt /Linux的86 /臂-EABI-4.4.0 / bin中/ ARM-EABI-GCC我认为对吗？该实用程序将正确配置一个库？如果是的，然后问题2：我试图编译这样一个库：libao。使用这...
gcc、arm-linux-gcc和arm-elf-gcc的关系？
关注微信公众号【开源Linux】，后台回复『10T』，领取10T学习资源大放送，涵盖Linux、虚拟化、容器、云计算、网络、Python、Go等书籍和视频
08-13 289
关注「开源Linux」，选择“设为星标” 回复「学习」，有我为您特别筛选的学习资料~ 转自：https://blog.youkuaiyun.com/ce123_zhouwei/article...
arm-elf和arm-eabi的区别
linux内核探索
08-17 1万+
文章链接：http://embdev.net/topic/129737我是从这个链接中看到的。觉得有点意思。因为自己用交叉编译器编译的时候。会出现arm-elf,arm-none-eabi,arm-eabi这些选择，倒底它们有什么区别呢？what is difference between arm-elf and arm-eabi? Re: what is difference between arm-elf and arm-eabi? Author:
arm-eabi, arm-linux-androideabi, arm-linux-gnueabi, arm-none-linux-gnueabi工具链的区别
Sean
03-06 3560
链接工具命名方式为： arch-vendor-os-abi ， 即cpu构架， 供应商， 操作系统， abi类型 例如： 1、arm-none-linux-gnueabi  (ARM architecture, no vendor, linux OS, and the gnueabi ABI) 用于编译ARM架构的u-boot、linux内核、linux应用
arm-linux,arm-elf-交叉编译环境下载地址
热门推荐
陈志新的专栏
05-15 2万+
最常用的编译版本是arm-linux-gcc-3.4.1 和 arm-linux-3.3.2 的，现在的嵌入式开发基本上用的是这些，3.4.1的用于编译2.6的内核，而3.3.2的常用于编译busybox,和bootloader(u-boot),编译的版本配合不好的话就会出错，所以要选择好编译版本，如果这个版本不行的话，可以试试其他的版本,在uclinux上用的多的就是arm-elf-tools-
arm-eabi-gcc 和 arm-none-eabi-gcc 都是基于 GCC 的交叉编译器
usstmiracle的博客
11-27 5443
您提供的网站是 Arm GNU Toolchain 的官方网站，它提供了不同的主机操作系统和目标架构的交叉工具链。arm-eabi-gcc 和 arm-none-eabi-gcc 都是基于 GCC 的交叉编译器，用于编译 ARM 架构的嵌入式系统。您也可以在这个网页上找到更多的信息，如安装说明、源代码包、已知问题等。arm-eabi-gcc 交叉编译器。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值