https://bugs.kde.org/show_bug.cgi?id=476553
--- Comment #3 from Peter Klotz <peter.klot...@gmail.com> --- Created attachment 163036 --> https://bugs.kde.org/attachment.cgi?id=163036&action=edit Workaround to packge gdb Python script files It seems gdb in RHEL8 is not too old for packaging valgrind-monitor-def.py and valgrind-monitor.py. The initial comment in the bug points to a permission problem because the RPM build tries to incorrectly write the files into /usr/libexec/valgrind. In an RPM build the correct path would be '/home/user/rpmbuild/BUILDROOT/valgrind-3.22.0-1.x86_64/usr/libexec/valgrind', so the prefix is missing. The problem lies in the 'install-recursive' target of the build. This patch is just a workaround, that always sets the directory but it would not work if the user opted for --without-gdbscripts-dir. Maybe someone who has a deeper understanding of the Valgrind build mechanism can come up with a patch that works in all cases. -- You are receiving this mail because: You are watching all bug changes.
