[Bug other/116322] New: regenerate-opt-urls.py usage

[Bug other/116322] New: regenerate-opt-urls.py usage

[gjl at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116322

            Bug ID: 116322
           Summary: regenerate-opt-urls.py usage
           Product: gcc
           Version: 15.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: other
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gjl at gcc dot gnu.org
  Target Milestone: ---

$ ./regenerate-opt-urls.py  -h
usage: regenerate-opt-urls.py [-h] [--unit-test] base_html_dir src_gcc_dir

[...]

Usage (from build/gcc subdirectory):
  ../../src/gcc/regenerate-opt-urls.py HTML/gcc-14.0.0/ ../../src

Running the script terminates with an error:

$ ../../../source/gcc-master/gcc/regenerate-opt-urls.py HTML/gcc-15.0.0/
../../../source/gcc-master/
[...]
FileNotFoundError: [Errno 2] No such file or directory:
'HTML/gcc-15.0.0/gdc/Option-Index.html'

The problem is obviously that GCC hasn't been configured for D, which is clear
because the target does not support D.

The regenerate-opt-urls.py should document how to re-generate onyl specific
option files, namely the one that is associated to a changed .opt file
(somewhere in gcc/config/$target).

[Bug other/116322] regenerate-opt-urls.py usage

[sjames at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116322

Sam James <sjames at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mark at gcc dot gnu.org,
                   |                            |ppalka at gcc dot gnu.org

--- Comment #1 from Sam James <sjames at gcc dot gnu.org> ---
Yeah, right now, it requires all FEs to be enabled. We've been telling people
they can cheat by using the diff that the buildbot gives in its failure report
though.

[Bug other/116322] regenerate-opt-urls.py usage

[gjl at gcc dot gnu.org]

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.