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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=FApELIoG+6+iFajXKt15w3AF3QWtaA5TT0yVT42nJWYJ9haV9S7jc
	a5Mp07Aj86vDGw1XH66hVdLkPpXsrhGOqMGw9EXiUqtukx/zz3ihvWAWZsxXU/U0
	SM0Wa32XSl/LQQ574ZHYs8IQEc2dLoT/DXyq+CZvG0vAeLedjXoojE=
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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=nuAPv0h436qQtBXuYTVX84nBdiE=; b=GLYEGbRq+Si+Nr0jwYMcmsM1cpD1
	smuf67NqwiqaKLLsYwHP1SwEizbQQGEBwyhy174JmfOI8aQHHOtmTcs4m6ZWSlPk
	9UR8ueDcLGinL3MZQzrPy9um7TJkU0i04onYW0Kkwy/V7u/AC3+RT4LPTZQWfHqv
	issHSE0p7yAZjI8=
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.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO:	mho-02-ewr.mailhop.org
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX184kHv8XPD3GxFOcRJwBzRd
Date:	Wed, 16 Oct 2013 17:36:39 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: [ANNOUNCEMENT] Updated: make-4.0-1 (x86 and x86_64)
Message-ID:	<20131016213639.GC4370@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20100810175435 DOT GA27225 AT ednor DOT casa DOT cgf DOT cx> <20111202173631 DOT GA8373 AT ednor DOT casa DOT cgf DOT cx> <announce DOT 20131011171208 DOT GA3094 AT ednor DOT casa DOT cgf DOT cx> <l3gqk5$h1o$1 AT ger DOT gmane DOT org> <20131015194722 DOT GC2368 AT ednor DOT casa DOT cgf DOT cx> <l3m9k5$49r$1 AT ger DOT gmane DOT org>
MIME-Version:	1.0
In-Reply-To:	<l3m9k5$49r$1@ger.gmane.org>
User-Agent:	Mutt/1.5.20 (2009-06-14)

On Wed, Oct 16, 2013 at 10:59:31AM -0400, Rolf Campbell wrote:
>On 2013-10-15 15:47, Christopher Faylor wrote:
>> On Mon, Oct 14, 2013 at 09:12:48AM -0400, Rolf Campbell wrote:
>>> make -O -f m.mk
>>>
>>> Produces this output:
>>> fcntl(): Invalid argument
>>> touch all
>>>
>>> I've tried this using both the 32-bit version and 64-bit version of
>>> cygwin 1.7.25 with the same results.
>>
>> I can't test this right now but it will probably work better if you
>> redirect stdout/stderr to a file.  That's what the make testsuite does.
>> make apparently expects to be able to get a lock on console/tty which
>> isn't currently supported on Cygwin.
>
>I can confirm that piping the output to a file makes the error message 
>go away.

Corinna and I are discussing how to implement the missing functionality
in Cygwin.  I probably should have known that Linux allowed you to lock
ttys this way but it sure never occurred to me to implement it in Cygwin.

cgf

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

- Raw text -