X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=RKXNGgRBRzZ3IJZm
	JjdKe5EaAR1lKWineZf1aqylaFfXDdxTAKswoTvEsElxJfaNsj+0CddZ43jkW9tj
	HVZ16C9LKMC+y/uz4iaE9e8uNnzrcb5Vdat8MceC3c+l8SkIa+5Bq2u3Mvo3PdDX
	JvVOnDlJMtO58cfHfBPtaYDYxRY=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=DT4NUWwdRjpZmSLceg5NBH
	kRlQc=; b=P6vmImjDz22nuf6EF4IlBsvhgui/F6I54SLxXKjNLTDqIAJp9y4+Vv
	dA2wC6yX4Qh4yB9EgH4NB9juKIna0k2hiWosp1YkjjnyRtXWIC0/LRXtgF0r61m7
	0/Cby0aXi5XfjwLU8BEd/0m3IKPv1aKFJ0IA/GDjaEEu9YOZa46U0=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 spammy=H*MI:sk:868tys7, H*i:sk:868tys7, H*f:sk:868tys7
X-HELO: limerock02.mail.cornell.edu
X-CornellRouted: This message has been Routed already.
Subject: Re: lint kills _Noreturn
To: cygwin AT cygwin DOT com
References: <6fef0097-c076-2691-c4f9-2af5a050a17e AT cornell DOT edu> <86fut07qha DOT fsf AT gmail DOT com> <9c66686a-0af8-dbfe-7804-797df8aad7c6 AT cornell DOT edu> <868tys7kbw DOT fsf AT gmail DOT com>
From: Ken Brown <kbrown AT cornell DOT edu>
Message-ID: <90ad3e8c-5a34-9973-404f-5fc696dc1e7f@cornell.edu>
Date: Sun, 29 May 2016 18:24:19 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <868tys7kbw.fsf@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Cornell-Gauge: Gauge=XXXXX
X-IsSubscribed: yes

On 5/29/2016 3:09 PM, Andy Moreton wrote:
> On Sun 29 May 2016, Ken Brown wrote:
>
>> On 5/29/2016 12:56 PM, Andy Moreton wrote:
>>> On Sun 29 May 2016, Ken Brown wrote:
>>>
>>>> If lint is defined, then /usr/include/sys/cdefs.h defines _Noreturn as a macro
>>>> that expands to nothing.  Is this intentional?
>>>>
>>>> Simple test case:
>>>>
>>>> $ cat test.h
>>>> #define lint 1
>>>> #include <sys/cdefs.h>
>>>> _Noreturn void foo (void);
>>>>
>>>> $ gcc -E test.h | grep foo
>>>>          void foo (void);
>>>>
>>>>
>>>> Ken
>>>
>>> A traditional lint program may not support the new C11 keywords, but
>>> will define the 'lint' symbol. See, e.g.
>>>      http://www.unix.com/man-page/FreeBSD/1/lint
>>
>> But in the present context (see my second message), we're redefining C11
>> keywords even though __STDC_VERSION__ >= 201112L.
>
> Agreed, but that should only affect a lint program that understands C11.
> Any other program should simply not be defining lint in the first place.
>
>>> Surely the real problem here is a program which is not a lint executable
>>> defining 'lint' ?
>>
>> The program is emacs built from a git checkout of the master branch.  By
>> default the configure option --enable-gcc-checking is used, and this causes
>> lint to be defined in src/config.h.  It doesn't seem to be a problem on
>> platforms other than Cygwin; or at least it hasn't been reported.
>
> I saw your report of emacs bug#23640, and followed here. I think the
> real question is why the recent change to emacs configure.ac added a
> definition of lint - that seems wrong.

That was actually added about 4 years ago, in commit b8df54f, when the 
--enable-gcc-warnings option was first added.  The only thing that 
changed recently was that the warnings are enabled by default on a git 
checkout of master.

Ken

--
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