From: "Csaba Ráduly" <rcsaba@gmail.com>
To: Marco Atzeri <marco.atzeri@gmail.com>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: segfault on 32bit
Date: Tue, 7 Apr 2020 22:27:58 +0200 [thread overview]
Message-ID: <cd085881-e58b-073f-f27d-9329a1a056e7@gmail.com> (raw)
In-Reply-To: <ca08d279-db91-b423-019f-e5df552e610b@gmail.com>
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.
Csaba
--
You can get very substantial performance improvements
by not doing the right thing. - Scott Meyers, An Effective C++11/14 Sampler
So if you're looking for a completely portable, 100% standards-conformat way
to get the wrong information: this is what you want. - Scott Meyers (C++TDaWYK)
next prev parent reply other threads:[~2020-04-07 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 17:33 Marco Atzeri
2020-04-07 20:27 ` Csaba Ráduly [this message]
2020-04-08 8:34 ` Dropping 32 bit Cygwin? (was Re: segfault on 32bit) Corinna Vinschen
2020-04-08 8:45 ` Corinna Vinschen
2020-04-08 8:53 ` Sharuzzaman Ahmat Raslan
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=cd085881-e58b-073f-f27d-9329a1a056e7@gmail.com \
--to=rcsaba@gmail.com \
--cc=cygwin@cygwin.com \
--cc=marco.atzeri@gmail.com \
/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).