From: Tom Tromey <tom@tromey.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: Tom Tromey <tom@tromey.com>, GDB Patches <gdb-patches@sourceware.org>
Subject: Re: Move gdbsupport to the top level
Date: Fri, 12 Jul 2019 13:05:00 -0000 [thread overview]
Message-ID: <87muhj9zee.fsf@tromey.com> (raw)
In-Reply-To: <CA+=Sn1=EHOoz=-5iOhbMP7OSYhJqQKNaojrAnR7mwpoPjoM0Xw@mail.gmail.com> (Andrew Pinski's message of "Fri, 12 Jul 2019 00:17:37 -0700")
>>>>> "Andrew" == Andrew Pinski <pinskia@gmail.com> writes:
Andrew> On Thu, Jul 11, 2019 at 2:03 PM Tom Tromey <tom@tromey.com> wrote:
>>
>> This patch moves the gdbsupport directory to the top level. This is
>> the next step in the ongoing project to move gdbserver to the top
>> level.
>>
>> The bulk of this patch was created by "git mv gdb/gdbsupport gdbsupport".
>>
>> This patch then adds a build system to gdbsupport and wires it into
>> the top level. Then it changes gdb to use the top-level build.
Andrew> Isn't the top-level makefile also synced with GCC's (and newlib's)?
Andrew> Where GCC is techincally
Andrew> the maintainer of it?
Last time around I checked in the patches locally first and then I sent
them upstream.
I don't mind doing it the other way, if that's important for some
reason, but it's still better to get sign-off from the gdb side before
committing to doing it.
thanks,
Tom
next prev parent reply other threads:[~2019-07-12 13:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 21:03 Tom Tromey
2019-07-12 7:18 ` Andrew Pinski
2019-07-12 13:05 ` Tom Tromey [this message]
2019-07-15 20:10 ` Tom Tromey
2019-08-20 19:38 ` Pedro Alves
2019-08-20 20:22 ` Tom Tromey
2019-09-17 16:11 ` Tom Tromey
2019-09-17 16:16 ` Eli Zaretskii
2019-09-17 16:35 ` Tom Tromey
2019-09-17 16:45 ` Eli Zaretskii
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=87muhj9zee.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=pinskia@gmail.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