Hi Mark, > > I double-checked the GCC internals manual and all it says is: > > > > There files are generated from the '.opt' files and the generated > > HTML documentation by 'regenerate-opt-urls.py', and should be > > regenerated when adding new options, via manually invoking 'make > > regenerate-opt-urls'. > > > > So what is wrong here, how am I supposed to use it? > > That is how you are supposed to use it. > Or instead of make -C do cd .../obj/gcc; make regenerate-opt-urls. > > That assert triggering is odd. Could you add or change that into a > print(rel_path) so we can see what it really is?
Thanks for your suggestion. It choke on a backup file made by quilt(1) under .pc/ at the top level. I'm not sure if this is a supported use scenario, but I find it annoyoing anyway. Is the regeneration script supposed to look outside gcc/ even? Maciej
