From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6971 invoked by alias); 20 Jan 2015 18:36:56 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 6962 invoked by uid 89); 20 Jan 2015 18:36:55 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL autolearn=no version=3.3.2 X-HELO: mtaout29.012.net.il Received: from mtaout29.012.net.il (HELO mtaout29.012.net.il) (80.179.55.185) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 20 Jan 2015 18:36:53 +0000 Received: from conversion-daemon.mtaout29.012.net.il by mtaout29.012.net.il (HyperSendmail v2007.08) id <0NIH00E00NHYJ800@mtaout29.012.net.il> for gdb-patches@sourceware.org; Tue, 20 Jan 2015 20:33:26 +0200 (IST) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout29.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NIH00BJYNJP2430@mtaout29.012.net.il>; Tue, 20 Jan 2015 20:33:26 +0200 (IST) Date: Tue, 20 Jan 2015 18:36:00 -0000 From: Eli Zaretskii Subject: Re: Building the 7.8.90 pretest on MinGW In-reply-to: <20150120182741.GK4041@adacore.com> To: Joel Brobecker Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83lhkxwb7r.fsf@gnu.org> References: <83vbk82fkg.fsf@gnu.org> <83egqv2jq7.fsf@gnu.org> <20150120182741.GK4041@adacore.com> X-IsSubscribed: yes X-SW-Source: 2015-01/txt/msg00550.txt.bz2 > Date: Tue, 20 Jan 2015 19:27:41 +0100 > From: Joel Brobecker > Cc: gdb-patches@sourceware.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. What about just "cherry-picking" that single change? Or would that cause trouble further down the line, when we do update gnulib?