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=ceqhtlJ7MapT5ARa
	STcnv+RrFenK8IPED4wB42acPiAd7mLuxZFU041VwrD3LwO1Ih9Vj5xN/cfMRAJN
	CztboEmROgvw2P96EzLTayqdcscZuNw78qcqcIHsHfdCWzc0pdFxvUPBIGmtfNUV
	/OtpHGxRXQqBqV7v+R3Om5jjHqY=
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=G92ddv4mm5jk85dGBffLhG
	OC9tE=; b=JUEKDdZ/Vi2IenWCTMbjHMmL94GWJ7DRjkUMOIO66GjS1dMT5bPwPP
	3gHIR1uubk9acrLDHTCxQl612syI4nMUwnXqtiV8KffNVMg93MCH+KFjr5Nik6z9
	/Z4bRSfAH1PnH2lMyPyDY+7SlFRMs8Eowa2fTJSinvg1IAFWb/ooY=
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=-0.9 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=H*r:encrypted, Hx-languages-length:744, Says, claims
X-HELO: mailout08.t-online.de
Subject: Re: [Bug] __wait_status_to_int() is expected to be a macro
To: cygwin AT cygwin DOT com
References: <CA+fF77nK6EUSWe_jxnQpEcOBiX-+uTxhh4vwT86swiybMcxB2A AT mail DOT gmail DOT com>
From: =?UTF-8?Q?Hans-Bernhard_Br=c3=b6ker?= <HBBroeker AT t-online DOT de>
Message-ID: <0ec2d4a0-07e7-1c04-4efc-dbd0a21c077e@t-online.de>
Date: Fri, 8 Jun 2018 19:26:36 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <CA+fF77nK6EUSWe_jxnQpEcOBiX-+uTxhh4vwT86swiybMcxB2A@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Am 08.06.2018 um 17:16 schrieb Denis Nikiforov:
> /usr/include/boost/process/detail/posix/is_running.hpp:18:1: error:
> non-constant condition for static assertion
>   static_assert(!WIFEXITED(still_active), "Internal Error");
>   ^~~~~~~~~~~~~
> 
> __wait_status_to_int must be a macros but it's redefined as a function.

It must?  Says who, based on what standard document?

For starters, nobody gets to make any such claims about 
__wait_status_to_int(), because that's an internal implementation detail 
of Cygwin.  If at all, such a claim might be made about WIFEXITED(), 
which is a POSIX standard element.  But POSIX makes no such requirement, 
as far as I could see on short examination.

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