Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: mark.kettenis@xs4all.nl, brobecker@adacore.com,
	bauerman@br.ibm.com, andreolb@gmail.com,
	gdb-patches@sourceware.org
Subject: Re: [PATCH] PR exp/9103
Date: Wed, 18 Mar 2009 04:20:00 -0000	[thread overview]
Message-ID: <ud4cfqx7x.fsf@gnu.org> (raw)
In-Reply-To: <m363i7k0hh.fsf@fleche.redhat.com>

> Cc: mark.kettenis@xs4all.nl, brobecker@adacore.com, bauerman@br.ibm.com,
>         andreolb@gmail.com, gdb-patches@sourceware.org
> From: Tom Tromey <tromey@redhat.com>
> Date: Tue, 17 Mar 2009 20:50:50 -0600
> 
> Thanks, after this I noticed that the manual has a section on install
> requirements.  What do you think of the appended patch?

It's okay, but I have two comments:

> +@item iconv
> +@value{GDBN}'s features related to character sets require a
> +functioning @code{iconv} implementation.

I think it would be good here to add a cross-reference to where these
features are described, to make more clear what is at stake.

> +@value{GDBN}'s top-level @file{configure} and @file{Makefile} will
> +arrange to build Libiconv if a directory named @file{libiconv} appears
> +in the @file{src} directory.

`src'?  Ah, you are talking about the `src' tree that includes GDB,
Binutils, libiberty, bfd, etc., right?  I'm not sure this will be
clear to anyone who does not habitually build these packages out of
the same tree.  How about adding that you are talking about the the
`libiconv' directory being a sibling directory to `gdb' under the same
parent directory?  (Does it have to be called `src', btw?)


  reply	other threads:[~2009-03-18  4:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c3f94bcc0903101928g3d767b7ah60ac81e8b6f77de@mail.gmail.com>
2009-03-11 15:37 ` Andre Oliveira Loureiro do Baixo
2009-03-11 16:30   ` Daniel Jacobowitz
2009-03-11 17:09     ` Andre Oliveira Loureiro do Baixo
2009-03-11 17:13       ` Tom Tromey
2009-03-11 18:37         ` Andre Oliveira Loureiro do Baixo
2009-03-11 20:29           ` Thiago Jung Bauermann
2009-03-11 22:25             ` Tom Tromey
2009-03-12  1:11               ` Tom Tromey
2009-03-13 23:37                 ` Joel Brobecker
2009-03-13 23:38                   ` Joel Brobecker
2009-03-14  1:41                     ` Tom Tromey
2009-03-14  0:10                   ` Mark Kettenis
2009-03-17 20:06                     ` Tom Tromey
2009-03-17 22:12                       ` Eli Zaretskii
2009-03-18  3:07                         ` Tom Tromey
2009-03-18  4:20                           ` Eli Zaretskii [this message]
2009-03-18 17:11                             ` Tom Tromey
2009-03-18 20:30                               ` Eli Zaretskii
2009-03-18  0:46                       ` Joel Brobecker
2009-03-18  1:14                         ` Tom Tromey

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=ud4cfqx7x.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=andreolb@gmail.com \
    --cc=bauerman@br.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=tromey@redhat.com \
    /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