https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119266
--- Comment #9 from Sam James <sjames at gcc dot gnu.org> --- (In reply to Jason Merrill from comment #7) > (In reply to Sam James from comment #0) > > $ A=/usr/lib/gcc/x86_64-pc-linux-gnu/15/ > > $ > > B=/usr/lib/gcc/x86_64-pc-linux-gnu/lib/gcc/x86_64-pc-linux-gnu/15/include/g++-v15/bits/std.cc > > $ contrib/relpath.sh $A $B > > ../lib/gcc/x86_64-pc-linux-gnu/15/include/g++-v15/bits/std.cc > > That looks right to me given those A and B. > Or, rather, I get your point now (and what I was trying to make and got confused by): yes, this is how that path ends up in the JSON file, but clearly the B is wrong.
