From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: guile: guild compile hangs
Date: Tue, 27 Jun 2017 23:32:00 -0000 [thread overview]
Message-ID: <613e0625-aa15-9f32-9959-dd2e7e0c3c11@t-online.de> (raw)
In-Reply-To: <26e771b6-2cbc-a06d-2d96-fa2c7ab4f75f@gmail.com>
Am 27.06.2017 um 21:53 schrieb Marco Atzeri:
> On 26/06/2017 12:52, Marco Atzeri wrote:
>> On 26/06/2017 11:46, Marco Atzeri wrote:
>>> On 25/06/2017 23:22, Yaakov Selkowitz wrote:
>>>> On 2017-06-18 18:04, Yaakov Selkowitz wrote:
>>>>> Marco,
>>>>>
>>>>> With both Cygwin 2.8.0 and the latest snapshot, guild compile hangs.
>>>>> I'm seeing this in rebuilding either gnutls or even guile itself.
FWIW, it also hangs when trying to build gdb from GIT sources (in the
gdb/data-directory folder).
>> I see the issue at least on 2.0.
I see it with "current" of Cygwin, i.e. 2.0. The last time it worked
was May 20th, apparently. The first big install after that date, here,
was the big round of Python updae on May 27th.
>
> and the trace end in a very strange way
>
> 21 3048022 [main] guile 8828 fhandler_pipe::create: 0 =
> pipe([0x180313008, 0x180313318], 65536, 0x50000)
> 23 3048045 [main] guile 8828 pipe2: 0 = pipe2([5, 6], 0x40000)
> 133 3048178 [main] guile 8828 sigprocmask: 0 = sigprocmask (0, 0x0,
> 0x600053EA0)
> --- Process 8828 thread 9356 created
> 309 3048487 [unknown (0x248C)] guile 8828
> pthread::thread_init_wrapper: tid 0xFF7FCE00
>
> --
> 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
>
>
--
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:[~2017-06-27 23:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-18 23:04 Yaakov Selkowitz
2017-06-25 21:22 ` Yaakov Selkowitz
2017-06-26 9:46 ` Marco Atzeri
2017-06-26 10:52 ` Marco Atzeri
2017-06-27 19:53 ` Marco Atzeri
2017-06-27 23:32 ` Hans-Bernhard Bröker [this message]
2017-06-28 11:58 ` Marco Atzeri
2017-06-28 19:19 ` Hans-Bernhard Bröker
2017-06-28 19:45 ` Marco Atzeri
2017-06-29 17:47 ` Hans-Bernhard Bröker
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=613e0625-aa15-9f32-9959-dd2e7e0c3c11@t-online.de \
--to=hbbroeker@t-online.de \
--cc=cygwin@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).