On Apr 7 22:27, Csaba Ráduly via Cygwin wrote: > On 07/04/2020 19:33, Marco Atzeri via Cygwin wrote: > > while trying to build the 32bit version on python, > > I hit this never seen before issue: > > > > checking for %zd printf() format support... make: *** No targets > > specified and no makefile found. Stop. > > *** ERROR: make failed > > 4 [main] sh 18479 D:\cygwin32\bin\sh.exe: *** fatal error in > > forked process - WFSO timed out after longjmp > > 4 [main] sh 18479 D:\cygwin32\bin\sh.exe: *** fatal error in forked > > proces > > s - WFSO timed out after longjmp > > 72365 [main] sh 18479 cygwin_exception::open_stackdumpfile: Dumping > > stack trac > > e to sh.exe.stackdump > > 72365 [main] sh 18479 cygwin_exception::open_stackdumpfile: Dumping > > stack trac > > e to sh.exe.stackdump > > > > > > $ uname -svr > > CYGWIN_NT-10.0-WOW 3.1.4(0.340/5/3) 2020-02-19 08:45 > > > > what is a WFSO ? > > WaitForSingleObject, presumably.
Right. This looks like a fork problem. It's 32 bit, so we have to expect fork errors more often. Given how much the distro has grown, and given that the number of 32 bit systems is constantly shrinking, we should really start to think about dropping 32 bit support. Most users these days use 64 bit systems. Some use 32 bit Cygwin on 64 bit systems, which doesn't really make sense, except, maybe, to build 32 bit packages. These users can easily switch to 64 bit Cygwin. The access statistics indicate that real 32 bit systems only make less than 2% of installed systems. It's a lot of hassle to keep 32 bit Cygwin running for only a minor installation base. I'm not saying that we switch off 32 bit support right now, but maybe 2020 should be the last year of 32 bit support. Corinna -- Corinna Vinschen Cygwin Maintainer
signature.asc
Description: PGP signature
-- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
