From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: in-src-tree build regression [Re: [PATCH] Move gnulib to top level]
Date: Tue, 30 Jul 2019 18:20:00 -0000 [thread overview]
Message-ID: <20190730182039.GA5349@host1.jankratochvil.net> (raw)
In-Reply-To: <20190613124818.15130-1-tom@tromey.com>
On Thu, 13 Jun 2019 14:48:18 +0200, Tom Tromey wrote:
> This patch moves the gdb/gnulib subdirectory to the top level.
73cc72729a184f00bf6fc4d74684a8516ba6b683 is the first bad commit
commit 73cc72729a184f00bf6fc4d74684a8516ba6b683
Author: Tom Tromey <tom@tromey.com>
Date: Sun May 5 17:35:20 2019 -0600
Move gnulib to top level
./configure;make
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:10828: configure-gdb] Error 1
make[1]: Leaving directory '/home/jkratoch/redhat/gdb-test-regr'
make: *** [Makefile:852: all] Error 2
I do not mind myself, just reporting it worked in gdb-8.3 release.
Jan
next prev parent reply other threads:[~2019-07-30 18:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 12:48 [PATCH] Move gnulib to top level Tom Tromey
2019-06-13 13:29 ` Pedro Alves
2019-06-13 18:34 ` Tom Tromey
2019-06-14 19:02 ` Tom Tromey
2019-06-19 15:56 ` Tom de Vries
2019-06-21 13:00 ` Tom Tromey
2019-06-21 13:23 ` Andreas Schwab
2019-06-21 14:56 ` Tom Tromey
2019-07-30 18:20 ` Jan Kratochvil [this message]
2019-07-31 17:30 ` in-src-tree build regression [Re: [PATCH] Move gnulib to top level] 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=20190730182039.GA5349@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.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