From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Move gnulib to top level
Date: Thu, 13 Jun 2019 13:29:00 -0000 [thread overview]
Message-ID: <229bf3df-3fe3-60e1-cfec-448810839fa5@redhat.com> (raw)
In-Reply-To: <20190613124818.15130-1-tom@tromey.com>
On 6/13/19 1:48 PM, Tom Tromey wrote:
> This patch moves the gdb/gnulib subdirectory to the top level.
>
> It adjusts the top-level build system to build gnulib when necessary,
> and changes gdb to use this. However, gdbserver still builds its own
> copy of gnulib, just from the new source location.
>
> A small hack was needed to ensure that gnulib is only built when gdb
> is enabled. The Makefile only provides an ordering -- the directory
> must be mentioned in configdirs to actually be compiled at all.
>
> Most of the patch is just a "git mv" of gnulib, though a few minor
> path adjustments were needed in some files there.
>
Also, gnulib/configure.ac is using ACX_LARGEFILE now.
> Tested by the buildbot.
>
I think we'll need the following, though not necessarily
in this patch:
- a gnulib/README file
- to list gnulib in top/MAINTAINERS
LGTM.
I'm sure you know, but JIC, the top-level changes will
need to go to gcc too.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2019-06-13 13:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 12:48 Tom Tromey
2019-06-13 13:29 ` Pedro Alves [this message]
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 ` in-src-tree build regression [Re: [PATCH] Move gnulib to top level] Jan Kratochvil
2019-07-31 17:30 ` 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=229bf3df-3fe3-60e1-cfec-448810839fa5@redhat.com \
--to=palves@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