On Mon, 3 Jun 2024, David Malcolm wrote: > > Thank you for fixing this up. Is this a new requirement now for > > .opt > > file changes? > > Yes, as of GCC 14. > > I posted the objectives here: > https://gcc.gnu.org/pipermail/gcc-patches/2023-November/636060.html
Thank you for the pointer. > > Why does it have to be called by hand then rather than > > being a make dependency? > > IIRC, the idea is: > (a) to avoid requiring Python 3 as a build dependency, and > (b) to avoid requiring the HTML docs to be built before gcc's code can > be built > > since missing a few URLs is a relatively minor issue that we don't want > to complicate the build for. Understood. My overall experience with Python over the years has been very bad, with things breaking randomly depending on the phase of the moon, the tide, etc., so I think avoiding it as a build dependency in the field is a good idea. > Hence we decided to check for it in CI instead. > > Hope the trade-off sounds reasonable I have reviewed the thread referred and I note that a concern such as mine has already been raised in response to which you have added the `regenerate-opt-urls' make target (thanks!). I think it's a good direction given the circumstances, but I also think a more generic make target such as `generated-sources' or suchlike would be good having as an umbrella for any future additions we may make, and as one that might be easier to remember. Perhaps it could be a dependency for `all' even, in the maintainer mode (which I confess to be guilty of not regularly using though), along with any autoconf stuff, etc. Maciej
