Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Guinevere Larsen <guinevere@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] gdb/README: Refactor where build requirements are explained
Date: Fri, 06 Mar 2026 21:20:30 +0200	[thread overview]
Message-ID: <86seacu5mp.fsf@gnu.org> (raw)
In-Reply-To: <feb2891a-1a8b-49db-99e1-5bfc6a0832a4@redhat.com> (message from Guinevere Larsen on Fri, 6 Mar 2026 13:43:44 -0300)

> Date: Fri, 6 Mar 2026 13:43:44 -0300
> Cc: gdb-patches@sourceware.org
> From: Guinevere Larsen <guinevere@redhat.com>
> 
> On 3/6/26 11:25 AM, Eli Zaretskii wrote:
> > I'd put that a bit farther, right after this:
> >
> >       When you unpack the gdb-VERSION.tar.gz file, it will create a
> >    source directory called `gdb-VERSION'.
> >
> >    You can build GDB right in the source directory:
> >
> > 	cd gdb-VERSION
> > 	./configure --prefix=/usr/local   (or wherever you want)
> > 	make all install
> >
> > IMO, it's more natural, because it will directly follow the
> > instructions for building GDB.
> 
> I think it doesn't quite work there, because right after this it says 
> "but we don't recommend doing that, you should instead create a build 
> directory", so we are cutting build instructions in the middle

We could change the wording there as well.  (I always build in the
source tree, and don't have any problems with that, so "we don't
recommend" sounds like an exaggeration to me.)

> In my opinion we should place it first, as users (or at least I) would 
> probably run the commands and then continue reading as the scripts run, 
> to save a little bit of time.

That's okay, but then we should word it as prerequisites, perhaps with
a heading.

  reply	other threads:[~2026-03-06 19:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-05 18:29 [PATCH] gdb/README: Document GNU Make requirement Guinevere Larsen
2026-03-05 18:56 ` Eli Zaretskii
2026-03-05 19:03   ` Guinevere Larsen
2026-03-06  7:11     ` Eli Zaretskii
2026-03-05 19:01 ` Andrew Pinski
2026-03-06  7:10   ` Eli Zaretskii
2026-03-06 12:13 ` [PATCH v2] gdb/README: Refactor where build requirements are explained Guinevere Larsen
2026-03-06 14:25   ` Eli Zaretskii
2026-03-06 16:43     ` Guinevere Larsen
2026-03-06 19:20       ` Eli Zaretskii [this message]
2026-03-09 14:28   ` [PATCH v3] " Guinevere Larsen
2026-03-09 14:51     ` Eli Zaretskii
2026-03-09 16:27       ` Guinevere Larsen
2026-03-09 16:41         ` Eli Zaretskii
2026-03-09 16:58           ` Pierre Muller

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=86seacu5mp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=guinevere@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