update hosttools and move to poky 5

[nashif]

• zephyr-sdk: set maintainer and version
• meson: update to 1.7
• arc qemu: update for latest poky
• qemu: support legacy platforms
• qemu: update to 9.2.1
• support/hosttools: update for poky 5
• kernel: remove recipe
• poky: use poky 5.0.7
• ci: set tar options to avoid issues with permissions
• qemu: rename arc_qemu
• qemu: rename legacy_qemu
• qemu: rename xilinx qemu and update to work with poky 5

Fixes #849
Fixes #772
Fixes #719
Fixes zephyrproject-rtos/openocd#67
Fixes zephyrproject-rtos/openocd#68
Fixes zephyrproject-rtos/openocd#58

[stephanosio]

@nashif What was the rationale for upgrading to Poky 5? Now we are targeting glibc 2.39, which is too new for most distros ...

See #764 for common distro glibc versions.

[nashif]

@nashif What was the rationale for upgrading to Poky 5? Now we are targeting glibc 2.39, which is too new for most distros ...

See #764 for common distro glibc versions.

we were using an EOLed, unsupported version of poky that made moving to newest tools such as qemu very difficult.
Moved to an LTS release that supported until 2028, a release that constantly get updates and security maintenance.

See https://wiki.yoctoproject.org/wiki/Releases

As for supported distros, we need to balance maintainability of the SDK and keeping up with updates and fixes and what we support, so supporting every distro out there IMO should not be the goal.

[stephanosio]

As for supported distros, we need to balance maintainability of the SDK and keeping up with updates and fixes and what we support, so supporting every distro out there IMO should not be the goal.

Well, glibc 2.39 is so new that even Ubuntu 22.04 is going to be unsupported if the host tools were not fully self contained.

Now, regarding being self contained, it looks like the Poky glibc and dynamic linker are now actually working (IIRC, it had been broken for quite some time, which was why we were sticking with an older Poky/glibc) and the host tools are using the glibc provided by Poky, not the host system -- I even tested it on Ubuntu 16.04 with glibc 2.23 and everything seems to be working fine.

So, this is a non-issue for now. We just need to keep the toolchain builds, which are outside Poky, targeting a fairly old glibc.

[nashif]

Now, regarding being self contained, it looks like the Poky glibc and dynamic linker are now actually working (IIRC, it had been broken for quite some time, which was why we were sticking with an older Poky/glibc) and the host tools are using the glibc provided by Poky, not the host system -- I even tested it on Ubuntu 16.04 with glibc 2.23 and everything seems to be working fine.

So, this is a non-issue for now. We just need to keep the toolchain builds, which are outside Poky, targeting a fairly old glibc.

right, that is the main reason behind using poky for this, or else we could be just building the hosttools for ubuntu.