public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/99453] libstdc++*-gdb.py installation depends on library naming Date: Tue, 11 May 2021 19:50:46 +0000 [thread overview] Message-ID: <bug-99453-4-jdoQoWTsQP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99453-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99453 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:dbb87d6a9c37c8eca80d77782717a8144515c16d commit r11-8381-gdbb87d6a9c37c8eca80d77782717a8144515c16d Author: Philippe Blain <levraiphilippeblain@gmail.com> Date: Fri Mar 12 19:26:46 2021 -0500 libstdc++: Install libstdc++*-gdb.py more robustly [PR 99453] In order for GDB to auto-load the pretty printers, they must be installed as "libstdc++.$ext-gdb.py", where 'libstdc++.$ext' is the name of the object file that is loaded by GDB [1], i.e. the libstdc++ shared library. The approach taken in libstdc++-v3/python/Makefile.am is to loop over files matching 'libstdc++*' in $(DESTDIR)$(toolexeclibdir) and choose the last file matching that glob that is not a symlink, the Libtool '*.la' file or a Python file. That works fine for ELF targets where the matching names are: libstdc++.a libstdc++.so libstdc++.so.6 libstdc++.so.6.0.29 But not for macOS with: libstdc++.6.dylib libstdc++.a Or MinGW with: libstdc++-6.dll libstdc++.dll.a Try to make a better job at installing the pretty printers with the correct name by copying the approach taken by isl [2], that is, using a sed invocation on the Libtool-generated 'libstdc++.la' to read the correct name for the current platform. [1] https://sourceware.org/gdb/onlinedocs/gdb/objfile_002dgdbdotext-file.html [2] https://repo.or.cz/isl.git/blob/HEAD:/Makefile.am#l611 libstdc++-v3/ChangeLog: PR libstdc++/99453 * python/Makefile.am: Install libstdc++*-gdb.py more robustly. * python/Makefile.in: Regenerate. Co-authored-by: Jonathan Wakely <jwakely@redhat.com> (cherry picked from commit c2fc1702cb3a3d5cc9c40de47f63b4c8f3f1d09c)
next prev parent reply other threads:[~2021-05-11 19:50 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-07 16:04 [Bug libstdc++/99453] New: " redi at gcc dot gnu.org 2021-03-07 16:21 ` [Bug libstdc++/99453] " iains at gcc dot gnu.org 2021-03-07 16:34 ` redi at gcc dot gnu.org 2021-03-08 21:29 ` levraiphilippeblain at gmail dot com 2021-04-03 19:05 ` levraiphilippeblain at gmail dot com 2021-04-21 15:55 ` cvs-commit at gcc dot gnu.org 2021-04-21 15:56 ` redi at gcc dot gnu.org 2021-05-11 19:50 ` cvs-commit at gcc dot gnu.org [this message] 2021-05-11 20:01 ` redi at gcc dot gnu.org 2021-05-26 17:07 ` raj.khem at gmail dot com 2021-05-27 10:07 ` redi at gcc dot gnu.org 2021-05-27 10:16 ` ross at burtonini dot com 2021-05-27 10:18 ` redi at gcc dot gnu.org 2021-05-27 10:26 ` redi at gcc dot gnu.org 2021-05-27 10:30 ` redi at gcc dot gnu.org 2021-05-27 12:14 ` levraiphilippeblain at gmail dot com 2021-05-27 16:39 ` redi at gcc dot gnu.org 2021-06-01 12:29 ` cvs-commit at gcc dot gnu.org 2021-06-02 13:43 ` cvs-commit at gcc dot gnu.org 2021-06-03 14:57 ` cvs-commit at gcc dot gnu.org 2021-06-03 14:57 ` cvs-commit at gcc dot gnu.org 2021-06-03 14:59 ` redi at gcc dot gnu.org 2022-05-09 16:19 ` redi at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-99453-4-jdoQoWTsQP@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).