From: Peter Dons Tychsen <pdt@dontech.dk>
To: Takashi Yano <takashi.yano@nifty.ne.jp>, cygwin@cygwin.com
Subject: Re: fork: Resource temporarily unavailable errors after upgrading cygwin packages
Date: Tue, 11 Feb 2020 10:38:00 -0000 [thread overview]
Message-ID: <b3f992f6b2ba69b9f29e2b126e8580e76d98e4a8.camel@dontech.dk> (raw)
In-Reply-To: <20200211112026.05664f5c68b6282a39da8ac2@nifty.ne.jp>
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
next prev parent reply other threads:[~2020-02-11 10:38 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6d43c714-c4ba-4f0c-9913-cb8453129c85@gmail.com>
[not found] ` <d24aa066-ab3d-9ff0-215a-0a1ed1ec2e5d@cornell.edu>
2020-01-01 22:32 ` David Finnie
2020-01-01 23:43 ` David Finnie
2020-01-02 3:02 ` Ken Brown
2020-01-02 21:58 ` Peter Dons Tychsen
2020-01-02 22:29 ` David Finnie
2020-01-02 22:40 ` Ken Brown
2020-02-05 21:46 ` Peter Dons Tychsen
2020-02-05 22:07 ` Ken Brown
2020-02-06 0:07 ` Takashi Yano
2020-02-05 22:18 ` David Finnie
2020-02-05 22:31 ` Ken Brown
2020-02-05 23:07 ` David Finnie
2020-02-05 23:35 ` Ken Brown
2020-02-07 18:13 ` Brian Inglis
2020-02-07 21:44 ` David Finnie
2020-02-10 20:58 ` Peter Dons Tychsen
2020-02-10 21:34 ` David Finnie
2020-02-11 2:21 ` Takashi Yano
2020-02-11 10:38 ` Peter Dons Tychsen [this message]
2020-02-11 10:40 ` Peter Dons Tychsen
2020-02-11 13:16 ` Takashi Yano
2020-02-11 14:21 ` Ken Brown
2020-02-12 14:40 ` Takashi Yano
2020-02-11 21:31 ` Peter Dons Tychsen
2020-02-12 2:25 ` Takashi Yano
2020-02-12 7:50 ` Corinna Vinschen
[not found] ` <20200212112411.32f05ee5ce2c1401bd076746@nifty.ne.jp>
[not found] ` <3971cde6277a16cb04ac25067b4478b9cfbfa319.camel@dontech.dk>
2020-02-13 4:14 ` Takashi Yano
2020-02-13 21:42 ` Peter Dons Tychsen
2020-02-14 1:25 ` Takashi Yano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b3f992f6b2ba69b9f29e2b126e8580e76d98e4a8.camel@dontech.dk \
--to=pdt@dontech.dk \
--cc=cygwin@cygwin.com \
--cc=takashi.yano@nifty.ne.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).