From: Simon Marchi <simark@simark.ca>
To: Joel Brobecker <brobecker@adacore.com>,
Wadud Miah <wadud.miah@nag.co.uk>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>,
Tom Tromey <tromey@adacore.com>
Subject: Re: building GDB 9.0.50.20191206
Date: Fri, 13 Dec 2019 19:53:00 -0000 [thread overview]
Message-ID: <ccdcc5ec-48df-82a3-f530-1ec61080c66d@simark.ca> (raw)
In-Reply-To: <20191212140954.GC8591@adacore.com>
On 2019-12-12 9:09 a.m., Joel Brobecker wrote:
> Hello,
>
>> I am trying to build GDB 9.0.50.20191206 from source and am getting the following error:
>>
>> configure: error: source directory already configured; run "make distclean" there first
>> configure: error: .././../../gnulib/configure failed for build-gnulib-gdbserver
>> configure: error: ./configure failed for gdbserver
>> make[1]: *** [Makefile:9534: configure-gdb] Error 1
>> make[1]: Leaving directory '/usr/local/src/gdb-9.0.50.20191206'
>> make: *** [Makefile:852: all] Error 2
>>
>> I don't need the server component of GDB as I will be debugging locally, but could not find any option in the configure script to disable the building of the server component. Any help will be greatly appreciated.
>
> Let me point you to the message I sent following the announcement of
> the availability of the first pre-release:
> https://www.sourceware.org/ml/gdb-patches/2019-12/msg00451.html
>
> I apologize for the message about the branch being created not
> but that's because these are automated, and I didn't know about
> that issue at the time the branch was created.
>
> --
> Joel
>
Adding Tom in CC.
Tom, could you describe what is missing to complete this move?
I am afraid that if we release like this, we'll get this question a ton of time, it wouldn't
be a good user experience at all. So it would be good to either:
(1) complete the move before the release
(2) make it official that building in the source directory is not supported from now on (this
idea was brought up a few times in the past), make configure fail when trying to do so
with a clear error message
Please tell me if there's anything I can do to help with this effort.
Simon
next prev parent reply other threads:[~2019-12-13 19:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 10:47 Wadud Miah
2019-12-12 14:10 ` Joel Brobecker
2019-12-12 14:22 ` Wadud Miah
2019-12-13 19:53 ` Simon Marchi [this message]
2019-12-13 20:01 ` Tom Tromey
2019-12-13 20:21 ` Simon Marchi
2019-12-13 23:25 ` Tom Tromey
2019-12-15 16:17 ` Tom Tromey
2019-12-17 6:01 ` Joel Brobecker
2019-12-18 20:23 ` Tom Tromey
2019-12-14 17:29 ` Christian Biesinger via gdb
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=ccdcc5ec-48df-82a3-f530-1ec61080c66d@simark.ca \
--to=simark@simark.ca \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=tromey@adacore.com \
--cc=wadud.miah@nag.co.uk \
/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