Closed nosnilmot closed 1 year ago
Thanks.
You're editing the crosstool-NG configuration to update their zlib version as well. Is that necessary to make the build succeed? Otherwise I'd suggest omitting that change (the toolchain's zlib isn't actually used by the resulting binaries).
You're editing the crosstool-NG configuration to update their zlib version as well. Is that necessary to make the build succeed? Otherwise I'd suggest omitting that change (the toolchain's zlib isn't actually used by the resulting binaries).
yes, it is necessary, otherwise crosstool-ng also fails to download zlib-1.2.12 because it's also looking for it at https://zlib.net/zlib-1.2.12.tar.xz (https://github.com/crosstool-ng/crosstool-ng/issues/1832). I could omit the CT_ZLIB_VERSION change and just update CT_ZLIB_MIRRORS to get 1.2.12 from the archives (fossils) but if making changes in that area we might as well use the version that does not have a vulnerability :)
Ok, thanks 👍🏻
Update zlib to 1.2.13 to address CVE-2022-37434
Also change zlib download to use archive URL so builds do not fail when specified version is no longer the current version, and therefore no longer available to download at default location
And reduce log output: