From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 45587 invoked by alias); 11 Feb 2020 10:38:42 -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 45576 invoked by uid 89); 11 Feb 2020 10:38:41 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.1 spammy=garbage, HX-Languages-Length:1110 X-HELO: relay.telenor.dk Received: from relay.telenor.dk (HELO relay.telenor.dk) (212.88.64.55) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 11 Feb 2020 10:38:39 +0000 X-MtScore: NO score=0 Received: from donpedro.P-2601HN-F1 (unknown [94.147.60.8]) by relay.telenor.dk (Telenor Denmark) with ESMTP id 79078C0E7522; Tue, 11 Feb 2020 11:38:35 +0100 (CET) Message-ID: Subject: Re: fork: Resource temporarily unavailable errors after upgrading cygwin packages From: Peter Dons Tychsen Reply-To: pdt@dontech.dk To: Takashi Yano , cygwin@cygwin.com Date: Tue, 11 Feb 2020 10:38:00 -0000 In-Reply-To: <20200211112026.05664f5c68b6282a39da8ac2@nifty.ne.jp> References: <6d43c714-c4ba-4f0c-9913-cb8453129c85@gmail.com> <93562f34-3a14-0c10-cb57-1ae861307d82@gmail.com> <810b0c97ee0697c06bdaa4dff4081bb502bc46ab.camel@dontech.dk> <9ed4b0776323e4a0f62191121715d52a0429bdb2.camel@dontech.dk> <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 X-SW-Source: 2020-02/txt/msg00096.txt.bz2 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