https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116322
--- Comment #2 from Georg-Johann Lay <gjl at gcc dot gnu.org> --- And it may be easier to use when we had a $builddir/gcc/regenerate-opt-urls.py built by configure 1) $builddir/gcc/regenerate-opt-urls.py would know where $srcdir is. 2) $builddir/gcc/regenerate-opt-urls.py would know what HTML/$version to use and could issue an error to run "make html" when it does not exist. 3) Shebang like #!/usr/bin/env python3 may not work on some build machines even when they have Python3 installed. configure can find a required Python version or higher: AM_PATH_PYTHON([<version>], [AC_MSG_NOTICE([using $PYTHON to run regenerate-opt-urls.py])]) AC_CONFIG_FILES([regenerate-opt-urls.py], [chmod +x regenerate-opt-urls.py]) Though GCC is using some older version of autotools, and I don't know how well and reliable AM_PATH_PYTHON works there.
