From: Eli Zaretskii <eliz@gnu.org>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: brobecker@adacore.com, simark@simark.ca,
gdb-patches@sourceware.org, tom@tromey.com
Subject: Re: [RFA/gdb-9-branch] Abort configure immediately if building GDB in tree
Date: Fri, 31 Jan 2020 08:55:00 -0000 [thread overview]
Message-ID: <834kwcm63u.fsf@gnu.org> (raw)
In-Reply-To: <87imksmz79.fsf@redhat.com> (message from Sergio Durigan Junior on Thu, 30 Jan 2020 16:06:18 -0500)
> From: Sergio Durigan Junior <sergiodj@redhat.com>
> Cc: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>
> Date: Thu, 30 Jan 2020 16:06:18 -0500
>
> $ ./src-release.sh -x gdb
> ==> Cleaning sources.
> ==> Making gdb-9.0.90.20200130/
> ==> configure --target=i386-pc-linux-gnu --disable-binutils --disable-gas --disable-gold --disable-gprof --disable-ld --enable-gdb --enable-libctf --enable-libdecnumber --enable-readline --enable-sim
> configure: error: GDB must be configured and built in a directory separate from its sources.
> ...
>
> I'm wondering what to do here. I think I found a hacky and ugly
> solution here, but I'm trying to see if there's a better approach.
A special command-line switch to 'configure', to be used by
src-release.sh?
next prev parent reply other threads:[~2020-01-31 7:35 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
2020-01-17 18:43 ` Joel Brobecker
2020-01-30 22:56 ` Sergio Durigan Junior
2020-01-31 8:55 ` Eli Zaretskii [this message]
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=834kwcm63u.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.com \
--cc=simark@simark.ca \
--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