From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 63534 invoked by alias); 17 May 2017 14:31:39 -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 61963 invoked by uid 89); 17 May 2017 14:31:37 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy= X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 17 May 2017 14:31:36 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 4097237F23; Wed, 17 May 2017 10:31:38 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id T4G3DUF3nRaw; Wed, 17 May 2017 10:31:38 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 188D537F1F; Wed, 17 May 2017 10:31:38 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 4A1B18031E; Wed, 17 May 2017 07:31:36 -0700 (PDT) Date: Wed, 17 May 2017 14:31:00 -0000 From: Joel Brobecker To: Eli Zaretskii Cc: Simon Marchi , gdb-patches@sourceware.org Subject: Re: GDB 7.99.91 MinGW compilation error in cli-script.c Message-ID: <20170517143136.mdnstf2u2jiydvnd@adacore.com> References: <20170504194442.63AAF60B72@joel.gnat.com> <83o9v3cs25.fsf@gnu.org> <91d9fc6cc7c07674a0b5cd02e7b1502b@polymtl.ca> <8360h38r1r.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8360h38r1r.fsf@gnu.org> User-Agent: NeoMutt/20170113 (1.7.2) X-SW-Source: 2017-05/txt/msg00394.txt.bz2 > > I think the best solution would be a check at configure time. I think > > it's a function that can be quite handy, so it would be unfortunate if > > we had to avoid using it, especially if it's easy to implement ourselves > > for MinGW. A configure check would be more robust than checking for > > MinGW or _GLIBCXX_HAVE_BROKEN_VSWPRINTF specifically, in case another > > platform needs the replacement too, or if the define changes at some > > point. > > I've meanwhile learned that the latest release 5.0 of MinGW runtime > solves this problem. Version 5.0 was first release Oct of 2016, so about 6 months ago. Is that sufficient to consider this issue as being resolved, or do we consider it as blocking for the 8.0 release? -- Joel