Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: Simon Marchi <simark@simark.ca>
Cc: Tom Tromey <tromey@adacore.com>,
	 Joel Brobecker <brobecker@adacore.com>,
	 Wadud Miah <wadud.miah@nag.co.uk>,
	 "gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: building GDB 9.0.50.20191206
Date: Fri, 13 Dec 2019 23:25:00 -0000	[thread overview]
Message-ID: <871rt7vme9.fsf@tromey.com> (raw)
In-Reply-To: <986c3939-b6fd-b973-0ccb-1bd91f097df2@simark.ca> (Simon Marchi's	message of "Fri, 13 Dec 2019 15:21:35 -0500")

>>>>> "Simon" == Simon Marchi <simark@simark.ca> writes:

Simon> On 2019-12-13 3:01 p.m., Tom Tromey wrote:
Simon> Tom, could you describe what is missing to complete this move?
>> 
>> Completing the move of gdbsupport and then gdbserver to top-level.

Simon> Yes, I understand that doing the move is necessary to complete the move :) ?  But are
Simon> there some known technical difficulties in doing it?

I'm sorry about the terse reply earlier.

The patch to move gdbsupport is here:

    https://sourceware.org/ml/gdb-patches/2019-07/msg00337.html

Review here:

    https://sourceware.org/ml/gdb-patches/2019-08/msg00433.html

Maybe some comments there still need to be addressed.  I can't recall
offhand.


Then comes the patch to move gdbserver.  This is pretty much mechanical,
I think.

Finally comes a patch to make gdbserver use the top-level gnulib and
gdbsupport.  This is mildly tricky due to type mismatches.

I've written all of these but they definitely need rebasing (which is
often nearly equivalent to rewriting them) and probably other tweaks as
well.

I wouldn't recommend this for gdb 9, but it does seem like a good idea
to start on these now, so that we have time to iron out the bugs.

Tom


  reply	other threads:[~2019-12-13 23:25 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
2019-12-13 20:01     ` Tom Tromey
2019-12-13 20:21       ` Simon Marchi
2019-12-13 23:25         ` Tom Tromey [this message]
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=871rt7vme9.fsf@tromey.com \
    --to=tromey@adacore.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=simark@simark.ca \
    --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