From: Simon Marchi <simark@simark.ca>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>
Subject: Re: [RFA/gdb-9-branch] Abort configure immediately if building GDB in tree
Date: Fri, 17 Jan 2020 18:24:00 -0000 [thread overview]
Message-ID: <b815958d-a091-97cf-2952-2884defa97ca@simark.ca> (raw)
In-Reply-To: <20200117181554.GB7007@adacore.com>
On 2020-01-17 1:15 p.m., Joel Brobecker wrote:
> Hi Simon,
>
> Thanks for the review.
>
>>> +if test x"${enable_gdb}" != x"no"; then
>>> + # For this branch, we do not support building GDB in-tree.
>>> + # Try to detect whether we are in this situation or not by
>>> + # searching for a couple of known files in the source directory.
>>> + if test -f gnulib/update-gnulib.sh -a -f gdb/ChangeLog; then
>>> + AC_MSG_ERROR([GDB must be configured and built in a directory separate from its sources])
>>
>> Finish the message with a period?
>
> Of course! FWIW, I modeled this to other calls to AC_MSG_ERROR ;-)
>
>> Some people who only know the "./configure && make && make install" recipe
>> might not know how (or that it's even possible) to configure and build in a
>> separate directory, so they'll be stuck there. I think it would be helpful
>> to give an example of how to do that, like:
>>
>> GDB must be configured and built in a directory separate from its sources.
>>
>> To do so, create a dedicated directory for your GDB build and invoke the configure
>> script from that directory:
>>
>> $ mkdir my-gdb-build
>> $ cd my-gdb-build
>> $ ../path/to/gdb-x.y.z/configure [configure args]
>> $ make
>>
>> Otherwise, that looks good to me.
>
> Attached is a revised patch. I chose to use the same sequence as
> the one in gdb/README, just for consistency.
LGTM, thanks!
next prev parent reply other threads:[~2020-01-17 18:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-05 7:30 Joel Brobecker
2020-01-06 3:06 ` Simon Marchi
2020-01-17 18:24 ` Joel Brobecker
2020-01-17 18:24 ` Simon Marchi [this message]
2020-01-17 18:43 ` Joel Brobecker
2020-01-30 22:56 ` Sergio Durigan Junior
2020-01-31 8:55 ` Eli Zaretskii
2020-01-31 21:02 ` Sergio Durigan Junior
2020-01-31 22:52 ` Sergio Durigan Junior
2020-02-01 7:24 ` Eli Zaretskii
2020-02-01 10:19 ` Joel Brobecker
2020-02-01 10:26 ` Joel Brobecker
2020-02-01 20:38 ` Sergio Durigan Junior
2020-01-17 18:26 ` 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=b815958d-a091-97cf-2952-2884defa97ca@simark.ca \
--to=simark@simark.ca \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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