From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: Building the 7.8.90 pretest on MinGW
Date: Tue, 20 Jan 2015 18:27:00 -0000 [thread overview]
Message-ID: <20150120182741.GK4041@adacore.com> (raw)
In-Reply-To: <83egqv2jq7.fsf@gnu.org>
> The gnulib problem was fixed upstream, see
>
> http://lists.gnu.org/archive/html/bug-gnulib/2015-01/msg00044.html
>
> Can we please import that fix into GDB, so that the next releases will
> not have the problem? (I don't know how to import from gnulib, let
> alone do it for just some of the modules.)
No one's really answered, so I'll provide some feedback: We can add
one or more modules, but I'm pretty sure the code for all modules need
to be from the same version of gnulib. This means we need to import
a more recent version of gnulib, but IIRC, the past few upgrades
haven't always been completely smooth (although, perhaps it was
more about the fact that we were adding new modules, rather than
the fact that we were upgrading). In any case, doing the upgrade
itself is fairly simple, but one needs to have enough time afterwards
to follow up on any issues that come up from the update.
I'd do it for you, but I don't have much of the time to followup
on any breakage caused by it. If others are willing to help with
that, I could give the gnulib update a go.
--
Joel
next prev parent reply other threads:[~2015-01-20 18:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <announce.20150113122445.36DDE48E8A@joel.gnat.com>
2015-01-15 16:07 ` Eli Zaretskii
2015-01-15 19:49 ` Doug Evans
2015-01-19 17:48 ` Eli Zaretskii
2015-01-22 11:05 ` Pedro Alves
2015-01-22 16:09 ` Eli Zaretskii
2015-01-22 17:04 ` Pedro Alves
2015-01-22 17:27 ` Eli Zaretskii
2015-01-22 17:46 ` Pedro Alves
2015-01-22 18:30 ` Eli Zaretskii
2015-01-16 8:49 ` Eli Zaretskii
2015-01-20 18:27 ` Joel Brobecker [this message]
2015-01-20 18:36 ` Eli Zaretskii
2015-01-20 19:08 ` Joel Brobecker
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=20150120182741.GK4041@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--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