public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 10.1 release -- 2020-09-18 Update
Date: Mon, 28 Sep 2020 12:30:29 +0300	[thread overview]
Message-ID: <83imbymeoa.fsf@gnu.org> (raw)
In-Reply-To: <20200926173940.GB13066@adacore.com> (message from Joel Brobecker on Sat, 26 Sep 2020 10:39:40 -0700)

> Date: Sat, 26 Sep 2020 10:39:40 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
> 
> > I attach below the patch for our copy of Gnulib on the release
> > branch.  It works here.  (I will again ask you to kindly regenerate
> > the configure script(s) that depend on gnulib/import/m4/*.m4 files.)
> 
> The patch as you propose it is not enough, because you also need to
> regenerate the configury stuff. Also, I think that anyone re-rerunning
> the update-gnulib.sh script would end up overwriting your changes.
> 
> Rather than doing everything by hand and risk missing something,
> I just propose we take advantage of our update-gnulib.sh script
> instead. To do so, I've imported the commits from gnulib as patches,
> and then updated the update-gnulib.sh script to include those two
> import patches in the sequence. The patches had to be adjusted
> a bit to the layout in the import as opposed to in the repository
> of origin, but they are otherwise the same.
> 
> This is the first moment I've had to work on this, so the patch
> hasn't been tested on our Windows machines yet. I expected to be
> able to report on that mid-to-late next week. In the meantime,
> if you could test this patch in your environment, this would help us
> guarantee that things are good on your end too, now.

I've downloaded today's snapshot of the branch, applied the patches
you sent, and build GDB.  It builds cleanly and passes all the sanity
checks I tried.

So I think you can install this (provided that you can build GDB using
MinGW64).

Thanks, and sorry I couldn't be of more help in this matter.

  reply	other threads:[~2020-09-28  9:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18 23:46 Joel Brobecker
2020-09-19  1:37 ` Simon Marchi
2020-09-19 19:42   ` Joel Brobecker
2020-09-19 23:58     ` Simon Marchi
2020-09-19  7:41 ` Eli Zaretskii
2020-09-19 19:48   ` Joel Brobecker
2020-09-21 16:26     ` Eli Zaretskii
2020-09-26 17:39       ` Joel Brobecker
2020-09-28  9:30         ` Eli Zaretskii [this message]
2020-09-28 20:11           ` Joel Brobecker
2020-10-09 19:53             ` [pushed/gdb-10-branch] gnulib: fix stat/fstat build errors on old Windows version or using old MinGW Joel Brobecker
2020-09-20  1:03 ` GDB 10.1 release -- 2020-09-18 Update Simon Marchi
2020-09-20  6:09   ` Eli Zaretskii
2020-09-21 19:54 ` Simon Marchi
2020-09-23 13:39   ` Tom Tromey
2020-09-23 14:00     ` Simon Marchi

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=83imbymeoa.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).