From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22367 invoked by alias); 9 Jan 2019 18:14:45 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 22318 invoked by uid 89); 9 Jan 2019 18:14:39 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy=HX-HELO:sk:mail-it, jony, JonY X-HELO: mail-it1-f169.google.com Received: from mail-it1-f169.google.com (HELO mail-it1-f169.google.com) (209.85.166.169) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 09 Jan 2019 18:14:37 +0000 Received: by mail-it1-f169.google.com with SMTP id g85so13060387ita.3 for ; Wed, 09 Jan 2019 10:14:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=tvNGjKMPl34lxH/elkBZ595MDIXEOAYHM2qFVIxpJg8=; b=F4ylQRToQgm849tQWoPR1utu8UkkVMCEVS9JplB9vadSkPAVpmXXlN/3If3KTuX8CT quZOmb4yUX+KyBv/7qIarFdv4+Mfkmhp6aMfAxFeWfuHTe32Na8IapkF6jF6+xTrpHn5 bDMSnh9sOpOkH9/a6NltQxvM3MwjiwmQUOJC86sq2DJLCq1Ze9KuPrmO/mDTQuj53xmM B7Qtcn6bKcvOykCa5HRpaFqpi3mi0uDtOnCC81hfsccgoaTOUN9Rf+kdDnPzdJ0macxQ YpGmTV4g7roHvFQoKcio6O4hKhr96Sj3+1OEnUhw39I2KsI8AW28RJO8nvsGRrEAOeW2 2nWg== MIME-Version: 1.0 Received: by 2002:a4f:1fc4:0:0:0:0:0 with HTTP; Wed, 9 Jan 2019 10:14:34 -0800 (PST) In-Reply-To: <92c7e8c2-c440-1bb8-f329-23951d10dffe@gmail.com> References: <92c7e8c2-c440-1bb8-f329-23951d10dffe@gmail.com> From: Lee Date: Wed, 09 Jan 2019 18:14:00 -0000 Message-ID: Subject: Re: i686-w64-mingw32-gcc: LC_MESSAGES To: cygwin@cygwin.com Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-01/txt/msg00049.txt.bz2 On 1/9/19, JonY wrote: > On 1/8/19 9:26 PM, Lee wrote: >> http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/locale.h.html >> has a note for LC_MESSAGES: >> The functionality described is an extension to the ISO C standard. >> Application developers may make use of an extension as it is >> supported on all POSIX.1-2017-conforming systems. >> >> i686-w64-mingw32-gcc doesn't have LC_MESSAGES defined. >> Is that an oversight, something missing in windows, or .. ?? >> > > Windows MSVCR isn't POSIX nor ISO C compliant, so you shouldn't be > referring to opengroups, only against MSDN. What's a Windows MSVCR? Since the same program compiled with cygwins' gcc has LC_MESSAGES defined, I was guessing it was just a library thing and maybe it just hadn't been implemented in the mingw libraries yet.. but it sounds like it's not an oversight & Microsoft needs to support LC_MESSAGES before i686-w64-mingw32-gcc will. Is that about right? Thanks, Lee -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple