public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Cc: pdt@dontech.dk
Subject: Re: fork: Resource temporarily unavailable errors after upgrading cygwin packages
Date: Tue, 11 Feb 2020 02:21:00 -0000	[thread overview]
Message-ID: <20200211112026.05664f5c68b6282a39da8ac2@nifty.ne.jp> (raw)
In-Reply-To: <23d3cd65794886745e2070a1d1b74013418b0bd8.camel@dontech.dk>

On Mon, 10 Feb 2020 21:58:09 +0100
Peter Dons Tychsen wrote:
> 1) Put attached makefile somewhere
> 2) Download https://nuwen.net/files/mingw/mingw-17.1-without-git.exe
> and unzip it in same place.
> 3) Now run "make create"
> 4) Now run "make clean && make -j32". Try a couple of times.
> 
> -----------
> 
> a) If running via mintty - it hangs fairly quickly, and the task-
> manager will show hanging gcc's and sh's.

Thanks for the test case. 

With cygwin 3.1.2, I confirmed make stops for a minute at:

.....
.....
echo running thread 98
echo running thread 99
running thread 98
cc    -c -o hang.o hang.c
running thread 99
MinGW/bin/gcc -MP -MM -MT test98.d -M -o test98.d test98.c && MinGW/bin/gcc -c -
o test98.o test98.c
MinGW/bin/gcc -MP -MM -MT test99.d -M -o test99.d test99.c && MinGW/bin/gcc -c -
o test99.o test99.c
cc    -c -o test.o test.c

and displays following after a minute.

cc   hang.o test00.d test01.d test02.d test03.d test04.d test05.d test06.d test07.d test08.d test09.d test10.d test11.d test12.d test13.d test14.d test15.d test16.d test17.d test18.d test19.d test20.d test21.d test22.d test23.d test24.d test25.d test26.d test27.d test28.d test29.d test30.d test31.d test32.d test33.d test34.d test35.d test36.d test37.d test38.d test39.d test40.d test41.d test42.d test43.d test44.d test45.d test46.d test47.d test48.d test49.d test50.d test51.d test52.d test53.d test54.d test55.d test56.d test57.d test58.d test59.d test60.d test61.d test62.d test63.d test64.d test65.d test66.d test67.d test68.d test69.d test70.d test71.d test72.d test73.d test74.d test75.d test76.d test77.d test78.d test79.d test80.d test81.d test82.d test83.d test84.d test85.d test86.d test87.d test88.d test89.d test90.d test91.d test92.d test93.d test94.d test95.d test96.d test97.d test98.d test99.d   -o hang
/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
/usr/lib/gcc/x86_64-pc-cygwin/7.4.0/../../../../x86_64-pc-cygwin/bin/ld:test00.d:1: syntax error
collect2: error: ld returned 1 exit status
make: *** [<builtin>: hang] Error 1
make: *** Waiting for unfinished jobs....
rm hang.o test.o hang.c test.c

Is this the same as your problem?

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

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
/usr/lib/gcc/x86_64-pc-cygwin/7.4.0/../../../../x86_64-pc-cygwin/bin/ld:test00.d:1: syntax error
collect2: error: ld returned 1 exit status
make: *** [<builtin>: hang] Error 1
make: *** Waiting for unfinished jobs....

Is this as you expected?

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

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

  parent reply	other threads:[~2020-02-11  2:21 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 [this message]
2020-02-11 10:38                   ` Peter Dons Tychsen
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=20200211112026.05664f5c68b6282a39da8ac2@nifty.ne.jp \
    --to=takashi.yano@nifty.ne.jp \
    --cc=cygwin@cygwin.com \
    --cc=pdt@dontech.dk \
    /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).