From: Jim Reisert AD1C <jjreisert@alum.mit.edu>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST: Cygwin 3.1.0-0.3
Date: Thu, 05 Sep 2019 18:11:00 -0000 [thread overview]
Message-ID: <CAK-n8j4B9cpL9r+Y5gOO1b3carVFzuVcPW8o7VEi5kb0khqiMA@mail.gmail.com> (raw)
In-Reply-To: <CALK-3mKnHy5tGzi4kkf7CZ4m-6x1fGwBsk=bc8Jv1KFoU_reHA@mail.gmail.com>
Since I started using this version, I've been having some strange
hangs running g++ (called from make). The compilation just hangs
(probably at the link stage). The .o file is generated but the .exe
is not. If I remove the .o file and try again, sometimes it works.
I had been running the August 09 version of Cygwin at work and have
never seen the problem there.
Does this ring any bells for anyone? I just updated work to the 5
September test version, I'll see if the problem shows up.
--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us
--
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:[~2019-09-05 18:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 12:47 Corinna Vinschen
2019-08-29 16:51 ` Biswapriyo Nath
2019-08-30 8:11 ` Corinna Vinschen
2019-08-30 19:16 ` Takashi Yano
2019-08-30 20:21 ` Corinna Vinschen
2019-08-31 3:58 ` Biswapriyo Nath
2019-08-31 4:21 ` Takashi Yano
2019-09-01 6:32 ` Biswapriyo Nath
2019-09-02 8:17 ` Corinna Vinschen
2019-09-03 9:28 ` Biswapriyo Nath
2019-09-03 10:48 ` Corinna Vinschen
2019-09-05 18:11 ` Jim Reisert AD1C [this message]
2019-09-06 2:23 ` Ken Brown
2019-09-06 5:22 ` Jim Reisert AD1C
2019-09-06 10:03 ` Thomas Wolff
2019-09-07 3:32 ` Takashi Yano
2019-09-07 11:53 ` Thomas Wolff
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=CAK-n8j4B9cpL9r+Y5gOO1b3carVFzuVcPW8o7VEi5kb0khqiMA@mail.gmail.com \
--to=jjreisert@alum.mit.edu \
--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).