When following the build instructions, the ../../crosstool-ng/ct-ng build command in build-deps.sh fails, preventing the firmware from being built. This is a known issue in v1.24.0 of crosstool-ng. It has been fixed in the master branch, and there are several workarounds for fixing this with tagged releases.
The linked issue has the details, but I can confirm that modifying the config allowed build-deps.sh to work properly. This was tested on Debian 11 (bullseye). For reference, here's the command that would update the .config file to have the correct URLs:
sed -e 's|CT_ISL_MIRRORS=.*$|CT_ISL_MIRRORS="https://libisl.sourceforge.io"|' \
-e 's|CT_EXPAT_MIRRORS=.*$|CT_EXPAT_MIRRORS="https://github.com/libexpat/libexpat/releases/download/R_2_2_6"|' \
-i .config
This option seems safer than building from master, and cleaner than downloading files outside of our working directory (e.g., into ~/src). Besides that, putting the files in ~/src didn't actually work for me when I tried that workaround.
When following the build instructions, the
../../crosstool-ng/ct-ng buildcommand inbuild-deps.shfails, preventing the firmware from being built. This is a known issue in v1.24.0 of crosstool-ng. It has been fixed in the master branch, and there are several workarounds for fixing this with tagged releases.The linked issue has the details, but I can confirm that modifying the config allowed build-deps.sh to work properly. This was tested on Debian 11 (bullseye). For reference, here's the command that would update the .config file to have the correct URLs:
This option seems safer than building from master, and cleaner than downloading files outside of our working directory (e.g., into ~/src). Besides that, putting the files in ~/src didn't actually work for me when I tried that workaround.