Re: Build Gcc 14.2 for arm-none-eabi: Gcc git or source from ARM developer?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tuesday, 20 August 2024 20:37:21 BST Georg Gast wrote:
> Hi Gcc,
> 
> i tried to compile the gcc git repository 14.2 for arm-none-eabi. I
> successfully comiled it for x86_64-linux-gnu. So i tried the --
> build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=arm-none-eabi
> and various combinations with multilib i looked up in the internet. All
> failed.
> 
> As i saw in the release criteria for the next gcc 15.0 this platform
> (arm-none-eabi) is not first nor secondary tier, i ask myself: Can this
> only be compiled from the gcc source code from arm?
> 
> https://developer.arm.com/documentation/109845/13-3-Rel1/?lang=en
> 
> Thanks a lot!
> 
> Georg

I've been taking a stab at building riscv for the new raspberry pi pico2 so 
updated my arm-none-eabi (for original pico1) to see if same sources work for 
both. Seems so..

binutils-2.43
gcc-14.2.0
newlib-.4.0.20231231

..no patches required for arm/riscv32 with bleeding edge newlib.

foo@sdu:~/usr/src/QT$ /usr/local/QT/6500r/xgcc/arm-none-eabi/bin/arm-none-
eabi-gcc -v
Using built-in specs.
COLLECT_GCC=/usr/local/QT/6500r/xgcc/arm-none-eabi/bin/arm-none-eabi-gcc
COLLECT_LTO_WRAPPER=/usr/local/QT/6500r/xgcc/arm-none-eabi/libexec/gcc/arm-
none-eabi/14.2.0/lto-wrapper
Target: arm-none-eabi
Configured with: ../gcc-14.2.0/configure --prefix=/usr/local/QT/6500r/xgcc/arm-
none-eabi --enable-languages=c,c++ --target=arm-none-eabi --with-gnu-as --
with-gnu-ld --disable-nls --disable-shared --disable-threads --disable-tls --
with-newlib --with-arch=armv6
Thread model: single
Supported LTO compression algorithms: zlib
gcc version 14.2.0 (GCC) 
^^^same on x86_64 and aarch64 rpi4 and rpi5.

An actual arm cross is different. You can't build an rpi executable with the 
above: only for the pico (ie: embedded). For actual arm cross executables I 
use..

binutils-2.26.1
linux-4.19.66
gcc-14.2.0
glibc-2.28

..but I don''t really have a use for it: whilst it builds, it may not work. 
I've not tested it  in a long time and even when I did, it was little more 
than "Hello World".








[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux