DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:subject:from:reply-to:to:date
	:in-reply-to:references:content-type:mime-version
	:content-transfer-encoding; q=dns; s=default; b=UYZXX0DmnC6IXyGX
	PJbLf/RPJd71yqv2GhMWQfLi72Ot/PSIWgdnorlJb1165/V0bJ583pInBvbF0+i0
	KRxNGPRt6wmFkFCZWsuvoAyZeRNkIyiO4RbXH7P1S7nG5WgZVWT94BCSWtwyIULG
	u2fALbxfbWt5Bw2MSp4Z6Q0rLac=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <b3f992f6b2ba69b9f29e2b126e8580e76d98e4a8.camel@dontech.dk>
Subject: Re: fork: Resource temporarily unavailable errors after upgrading cygwin packages
From: Peter Dons Tychsen <pdt@dontech.dk>
Reply-To: pdt@dontech.dk
To: Takashi Yano <takashi.yano@nifty.ne.jp>, cygwin@cygwin.com
Date: Tue, 11 Feb 2020 11:38:35 +0100
In-Reply-To: <20200211112026.05664f5c68b6282a39da8ac2@nifty.ne.jp>
References: <6d43c714-c4ba-4f0c-9913-cb8453129c85@gmail.com>	 <d24aa066-ab3d-9ff0-215a-0a1ed1ec2e5d@cornell.edu>	 <93562f34-3a14-0c10-cb57-1ae861307d82@gmail.com>	 <f4a808cf-d129-f6ce-0da8-674cf88a71ad@gmail.com>	 <810b0c97ee0697c06bdaa4dff4081bb502bc46ab.camel@dontech.dk>	 <CACSsrOzmexPqVeAoZigrkR4Tv6sWa-506Ui8UzsgLcTSBotgLw@mail.gmail.com>	 <9ed4b0776323e4a0f62191121715d52a0429bdb2.camel@dontech.dk>	 <d5109f77-9d73-fd68-fac6-1119037c8468@gmail.com>	 <23d3cd65794886745e2070a1d1b74013418b0bd8.camel@dontech.dk>	 <20200211112026.05664f5c68b6282a39da8ac2@nifty.ne.jp>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.32.5 (3.32.5-1.fc30)
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit

Hi Takashi,

Thanks for looking at this & your great work on Cygwin!

On Tue, 2020-02-11 at 11:20 +0900, Takashi Yano wrote:
> Is this the same as your problem?

Yeah, it could be. Could this result in fork error messages as we are
seeing all over the place?

> If so, it goes without stopping 1 minute with patch:
> https://cygwin.com/ml/cygwin-patches/2020-q1/msg00148.html

Nice trick to use pinfo as a work-around, but i could fear that others
also call kill() at this critical time. Is there an actual fix for
kill() in the cooking? I could fear that tools like "make" actually
call this all over the place, especially if its aborting running
processes. And why did this work before?

> In any case, the following error occurs.
> 
> /usr/lib/gcc/x86_64-pc-cygwin/7.4.0/../../../../x86_64-pc-
> cygwin/bin/ld:test00.d: file format not recognized; treating as
> linker script

That looks OK. Ignore the actual result of the makefile, 
its just garbage :-). Its only to reproduce this error.

Thanks again for helping,

/pedro


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