https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115743
--- Comment #6 from Ralf Habacker <ralf.habacker at freenet dot de> --- Created attachment 58569 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58569&action=edit Logfile building gcc without patch (In reply to Andrew Pinski from comment #5) > Can you attach the resulting `libstdc++.*-gdb.py` file (without the patch > included) This is a bit tricky, as the packaging now fails and I cannot get the content of the file from remote build host. Instead I can show you what is replaced in the generated file. In the file 'hook.in' there is pythondir = '@pythondir@' libdir = '@toolexeclibdir@' and in the log file you can see which variables are replaced: [ 671s] make[4]: Entering directory '/home/abuild/rpmbuild/BUILD/gcc-13.2.0/build/i686-w64-mingw32/libstdc++-v3/python' [ 671s] sed -e 's,@pythondir@,/usr/i686-w64-mingw32/sys-root/mingw/share/gcc-13.2.0/python,' \ [ 671s] -e 's,@toolexeclibdir@,/usr/i686-w64-mingw32/sys-root/mingw/lib/gcc/i686-w64-mingw32/13.2.0,' < ../../../../libstdc++-v3/python/hook.in > gdb.py > and where it is located? [ 678s] /usr/bin/install -c -m 644 gdb.py /home/abuild/rpmbuild/BUILDROOT/mingw32-gcc-13.2.0-lp155.44.1.x86_64/usr/i686-w64-mingw32/sys-root/mingw/lib/gcc/i686-w64-mingw32/13.2.0/libstdc++.dll.a-gdb.py BTW: /home/abuild/rpmbuild/BUILDROOT/mingw32-gcc-13.2.0-lp155.44.1.x86_64 is the build root from which the packages are generated from
