public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/17180] New: "make uninstall" is broken Date: Fri, 18 Jul 2014 17:17:00 -0000 [thread overview] Message-ID: <bug-17180-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=17180 Bug ID: 17180 Summary: "make uninstall" is broken Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: dje at google dot com I was testing "make uninstall" and hit this: Entering directory .../gdb/gdbserver/build-libiberty-gdbserver No rule to make uninstall. Leaving directory ... [I had to manually copy that over, watch for typos.] Also, uninstallation of python data files doesn't remove .pyc files. repro: make install run installed gdb cd data-directory # to work around build-libiberty-gdbserver issue make uninstall ls -l $install/share/gdb/python/gdb -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2014-07-18 17:17 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-18 17:17 dje at google dot com [this message] 2022-04-08 2:03 ` [Bug gdb/17180] " tromey at sourceware dot 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-17180-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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).