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, 01 Jun 2021 12:29:40 +0000 [thread overview] Message-ID: <bug-99453-4-63AQeHgXgQ@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 #16 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:9f7bc160b4a0f27dce248d1226e3ae7104b0e67b commit r12-1141-g9f7bc160b4a0f27dce248d1226e3ae7104b0e67b Author: Jonathan Wakely <jwakely@redhat.com> Date: Tue Jun 1 11:00:16 2021 +0100 libstdc++: Fix installation of python hooks [PR 99453] When no shared library is installed, the new code to determine the name of the -gdb.py file yields an empty string. Use the name of the static library in that case. libstdc++-v3/ChangeLog: PR libstdc++/99453 * python/Makefile.am: Use archive name for printer hook if no dynamic library name is available. * python/Makefile.in: Regenerate.
next prev parent reply other threads:[~2021-06-01 12:29 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 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 [this message] 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-63AQeHgXgQ@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).