Re: ESP32 toolchain

[Rui-Xiang Guo <rxg%lavabit.com@localhost>]

On Mon, Dec 15, 2025 at 05:02:50PM +0100, Manuel Bouyer wrote:
> On Mon, Dec 15, 2025 at 10:50:58AM -0500, Greg Troxel wrote:
> > Fr?d?ric Fauberteau <triaxx%netbsd.org@localhost> writes:
> > 
> > > (cross/xtensa-esp-elf-{binutils, gcc}).
> > > Actually, the produced binary is a ELF 32-bit MSB executable. But it seems that ESP32 chips are little endian and the cross GCC should produce a LSB executable.
> > >
> > > Therefore I have packaged in wip another cross toolchain: wip/xtensa-esp32-elf-{binutils, gcc} that uses the Espressif overlays. It is based on cross/xtensa-esp-elf-{binutils, gcc}: thank you tnn@ for your initial packaging.
> > 
> > I am theoretically interested but have not gotten to this yet.
> > 
> > The larger situation is seeming messy, at least in my head.  I don't
> > think it's ok to add a package with a similar name and different
> > behavior without trying to resolve the confusion.
> > 
> > ESP is a vague name, covering at least esp8266 and esp32 as I hear it.
> > Do you believe that cross/xtensa-esp-elf-gcc is really for esp8266 only,
> > and that the esp8266 family really is big endian?  Are you proposing to
> > change the DESCR for that port?  To rename it to esp8266 or to explain
> > that 'esp' means 'esp8266'?
> 
> AFAIK, it's xtensa-lx106-elf* which is for esp8266.

BTW, there is another wip/xtensa-lx106-elf-gcc10 which is used by
wip/arduino-esp8266.

-rxg

> I tried using xtensa-esp-elf-gcc, before giving up because it's way too
> recent for the software I was trying to build (I ended up using the
> provided linux binary, which is a gcc 4.8-something). But from what I
> remember, xtensa-esp-elf-gcc supports multiple architectures, big and
> little-endian. You have to use the right gcc switch for your target.
> 
> -- 
> Manuel Bouyer <bouyer%antioche.eu.org@localhost>
>      NetBSD: 26 ans d'experience feront toujours la difference
> --