Chris Johns commented: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/161#note_145400 I think the issue maybe somewhere else? The `makeinfo` package has caused trouble in the past. GCC builds broke on older hosts with versions of the tool that did not support updated docs plus MacOS does not have the package and native Windows may not depending on the MSYS2 packages installed. As a result the RSB checks the `makeinfo` version and if it does not exist or is not recent enough it builds on internal version it from source. Not having `install-info` in the path with `makeinfo` looks to me like a broken packaging system? The trail is [rtems-default-tools.bset](https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/blob/main/rtems/config/tools/rtems-default-tools.bset) defined `%with_rtems_texinfo` and with `print/texinfo-internal` and that ends up in [bare/config/print/texinfo.cfg](https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/blob/main/bare/config/print/texinfo.cfg) and it has: ``` %define makeinfo_version 7.0.3 %define has_makeinfo %(makeinfo --version > /dev/null 2>&1; echo $?) %if %{has_makeinfo} == 0 %define makeinfo_version_resident \ %(makeinfo --version | grep -e "^makeinfo (GNU texinfo)" -e "^texi2any (GNU texinfo)" | rev | sed -r 's/ .*//' | rev) %if %{makeinfo_version_resident} < %{makeinfo_version} %define has_makeinfo 1 %endif %endif %if %{force_package_build} || %{has_makeinfo} != 0 %include %{_configdir}/print/texinfo-7.0.3.cfg %endif ``` The script checks if the tool is present and if it is it is the correct version. I suggest you raise a packaging bug with Microsoft and point out the issue and if that fails maybe add a check for `install-info` to this check? -- View it on GitLab: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/161#note_145400 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
