From: Daniel Jacobowitz <drow@false.org>
To: Brooks Moses <brooks@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch][gdb,etc] Add configure option to disable building internal documentation.
Date: Wed, 07 Nov 2007 02:54:00 -0000 [thread overview]
Message-ID: <20071107025356.GA1752@caradoc.them.org> (raw)
In-Reply-To: <4730F626.806@codesourcery.com>
On Tue, Nov 06, 2007 at 03:17:58PM -0800, Brooks Moses wrote:
> (I also have a corresponding patch for libiberty; my understanding is
> that this should go to GCC first, and then it will get merged to
> src/libiberty, yes?)
Yes.
> Tested by building gdb with various iterations of this flag, and
> confirming that it works as expected and doesn't break the build. Ok to
> commit?
No, sorry - as came up after you posted this, the GNU make requirement
is not OK for GDB or binutils. Could you revise?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-11-07 2:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 23:18 Brooks Moses
2007-11-07 2:54 ` Daniel Jacobowitz [this message]
2007-11-07 4:10 ` Eli Zaretskii
2007-11-07 19:22 ` Brooks Moses
2007-11-07 20:52 ` Joel Brobecker
2007-11-07 22:22 ` Eli Zaretskii
2007-11-07 23:50 ` Mark Kettenis
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=20071107025356.GA1752@caradoc.them.org \
--to=drow@false.org \
--cc=brooks@codesourcery.com \
--cc=gdb-patches@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: link
Be 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