public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "richard_sharman at mitel dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug build/17268] New: python directory not installed when makeinfo missing Date: Thu, 14 Aug 2014 13:14:00 -0000 [thread overview] Message-ID: <bug-17268-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=17268 Bug ID: 17268 Summary: python directory not installed when makeinfo missing Product: gdb Version: 7.6 Status: NEW Severity: normal Priority: P2 Component: build Assignee: unassigned at sourceware dot org Reporter: richard_sharman at mitel dot com After moving to centos 6.5 I rebuilt gdb 7.6. It seemed ok but the python direcotry ( /usr/local/share/gdb/python/gdb ) was empty. Checking the make install output showed it complained about missing makeinfo. I installed the textinfo package, re-configured made and installed gdb and now the python directory is present. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2014-08-14 13:14 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-14 13:14 richard_sharman at mitel dot com [this message] 2022-02-22 15:18 ` [Bug build/17268] " 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-17268-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).