update hosttools and move to poky 5 #871
Conversation
Update maintainer and version.
meson 1.7 needed for some of the tools. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
make old recipes work with latest poky. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Some targets were dropped or not supported in latest qemu, move them to a special legacy build for now. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Bump qemu to 9.2.1, using tarball for now, will go back to git repo maintained by us later. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Updates needed to make those recipes work with poky 5. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Removed unused recipe. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Use upstream and supported poky release Signed-off-by: Anas Nashif <anas.nashif@intel.com>
This happens in CI, a "fix" was also made in bitbake, but leaving this, just in case. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Rename recipe to be consistent with other recipes. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Rename recipe to be consistent. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Rename and modify to work with latest poky. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
|
@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. 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. |
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. |
right, that is the main reason behind using poky for this, or else we could be just building the hosttools for ubuntu. |
Fixes #849
Fixes #772
Fixes #719
Fixes zephyrproject-rtos/openocd#67
Fixes zephyrproject-rtos/openocd#68
Fixes zephyrproject-rtos/openocd#58