From: Marco Atzeri <marco.atzeri@gmail.com>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: update on python refreshing
Date: Sat, 23 May 2020 11:39:07 +0200 [thread overview]
Message-ID: <48d62533-a3e5-21f2-e0b9-f3841b77b406@gmail.com> (raw)
In-Reply-To: <e0e492ce-2523-d706-9f66-42a8f31d80bc@gmail.com>
On 23.05.2020 10:48, Marco Atzeri wrote:
> As I am blocked on the python update,
> I would like to inform you about the issue
>
> On i686 arch and only on that, in all versions
> 3.8.3 and 2.7.18 the sh.exe segfaults during configure
>
> The logs on 3.8.3 and also rebuilding 3.8.2
> -------------------------------------------
> checking for use_env... yes
> configure: checking for device files
> checking for /dev/ptmx... yes
> make: *** No targets specified and no makefile found. Stop.
> *** ERROR: make failed
> -------------------------------------------
>
> on 2.7.18:
> -------------------------------------------
> checking for /dev/ptmx... yes
> checking for /dev/ptc... no
> checking for %lld and %llu printf() format support... make: *** No
> targets specified and no makefile found. Stop.
> ESC[1;31m*** ERROR:ESC[0;0m make failed
> 15 [main] sh 6354 D:\cygwin32\bin\sh.exe: *** fatal error in
> forked process - WFSO timed out after longjmp
> 80937 [main] sh 6354 cygwin_exception::open_stackdumpfile: Dumping
> stack trace to sh.exe.stackdump
> -------------------------------------------
> In one of the 3 cases no stack dump is produced, while for the other
> two I have:
>
> $ cat sh.exe.stackdump
> Stack trace:
> Frame Function Args
> 006DC078 61084F28 (00000000, 77BE6DD2, 00777E68, 00770000)
>
> $ cat sh.exe.stackdump
> Stack trace:
> Frame Function Args
> 006DC438 61084F28 (00000148, 00000000, 00000000, 00000018)
> End of stack trace
>
> $ addr2line.exe -a 61084F28 -e /usr/bin/cygwin1.dll
> 0x61084f28
> /usr/src/debug/cygwin-3.1.4-1/winsup/cygwin/fork.cc:650
>
>
> As 3.8.2 was built before, it seems a recent change in Cygwin
> is impacting the 32bit platform.
>
>
> It seems I forgot the announce, but last build was 10th of April
> https://cygwin.com/packages/x86/python38/python38-3.8.2-1
>
> so I will try to bisect Cygwin to see when this problem arose.
>
> Crossing finger
> Marco
>
It seems I was lucky, current git does not have the problem
so I was able to build both 3.8.3 and 2.7.18
without any need for a bisect.
Give me some time for the packaging and I will update both
Regards
Marco
prev parent reply other threads:[~2020-05-23 9:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 8:48 Marco Atzeri
2020-05-23 9:39 ` Marco Atzeri [this message]
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=48d62533-a3e5-21f2-e0b9-f3841b77b406@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-apps@cygwin.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).