public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "aaro.koskinen at iki dot fi" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/14678] GDB 7.5 fails to build unless makeinfo is installed Date: Fri, 28 Jun 2013 18:12:00 -0000 [thread overview] Message-ID: <bug-14678-4717-r4102UcL3D@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-14678-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=14678 Aaro Koskinen <aaro.koskinen at iki dot fi> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aaro.koskinen at iki dot fi --- Comment #2 from Aaro Koskinen <aaro.koskinen at iki dot fi> --- I see the same error with GDB 7.5.1. This happens during "make install". There should be a way to prevent docs being installed. I'm cross-building GDB for 5 different targets, it's not like I would need a separate copy of documentation for each one of them in any case. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2013-06-28 18:12 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-06 19:17 [Bug gdb/14678] New: " psmith at gnu dot org 2013-01-02 18:57 ` [Bug gdb/14678] " palves at redhat dot com 2013-06-28 18:12 ` aaro.koskinen at iki dot fi [this message] 2020-03-07 19:18 ` psmith at gnu dot org 2020-03-07 19:22 ` psmith at gnu dot org 2020-11-21 20:48 ` miguel.ojeda.sandonis at gmail dot com 2022-02-22 15:18 ` tromey at sourceware dot org 2022-02-22 15:19 ` tromey at sourceware dot org 2022-02-22 15:19 ` tromey at sourceware dot org 2022-02-22 15:20 ` tromey at sourceware dot org 2022-02-23 15:12 ` [Bug build/14678] " tromey at sourceware dot org 2022-10-04 15:48 ` vries at gcc dot gnu.org 2022-10-19 1:43 ` Nick.Fall at outlook dot jp 2022-10-19 4:02 ` vries at gcc dot gnu.org 2023-08-28 7:55 ` bugmenot at mailinator dot com 2023-08-28 13:48 ` 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-14678-4717-r4102UcL3D@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).