From: Andrew Pinski <pinskia@gmail.com>
To: Tom Tromey <tom@tromey.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: Move gdbsupport to the top level
Date: Fri, 12 Jul 2019 07:18:00 -0000 [thread overview]
Message-ID: <CA+=Sn1=EHOoz=-5iOhbMP7OSYhJqQKNaojrAnR7mwpoPjoM0Xw@mail.gmail.com> (raw)
In-Reply-To: <87lfx4z3lx.fsf@tromey.com>
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.
Isn't the top-level makefile also synced with GCC's (and newlib's)?
Where GCC is techincally
the maintainer of it?
Thanks,
Andrew Pinski
>
> gdbserver, on the other hand, is not yet changed. It still does its
> own build of gdbsupport.
>
> I wasn't able to send this through the buildbot. I did test it on
> x86-64 Fedora 29. If you want to try it, it is on the branch
> submit/move-gdbsupport-to-top in my github.
>
>
> This patch was also too big to send the usual way, so I have compressed
> it and added it as an attachment. Sorry about that.
>
> Tom
>
next prev parent reply other threads:[~2019-07-12 7:18 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 [this message]
2019-07-12 13:05 ` Tom Tromey
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='CA+=Sn1=EHOoz=-5iOhbMP7OSYhJqQKNaojrAnR7mwpoPjoM0Xw@mail.gmail.com' \
--to=pinskia@gmail.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