public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Strange errors running gcc tests on Cygwin
Date: Sat, 18 Mar 2017 14:52:00 -0000	[thread overview]
Message-ID: <a710962e-4ac0-2bfb-5dbc-3945e16543af@gmail.com> (raw)
In-Reply-To: <4bef8263-bdd5-caa2-bada-c1662ef1005e@pobox.com>

On 3/18/2017 9:52 AM, Daniel Santos wrote:
> 
> Ok, thanks. I have a license for Windows 7 and while I know that Windows
> 10 is "free" I'm just not ready for that step.  I will probably have to
> eventually setup a win10 vm though.
> 

For me moving from Win7 to Win10 was no big deal other than the time for
the updates but that occurred in the background. However, if you're like
me I prefer not to be working during such updates.

>>> I'm also building the current cygwin1.dll from git as I've seen a few
>>> messages about bugs being fixed that could be related.
>> You can download Cygwin snapshots: dll only, dbg, pkg, src, directly from
>> https://cygwin.com/snapshots for x86{_64,} - instructions given on page.
> 
> Yeah, I usually prefer to build it myself.  I did test the git
> cygwin1.dll and it didn't fix the broken pipes (when running make check
> with more than one -j job).  As I've said before, I'm sure there's a
> race somewhere in Cygwin or some other Cygwin package(s). If I follow
> through with making this into a repeatable process, I'll likely have to
> try to diagnose it.

Glad to hear you're working to improve Cygwin.

-- 
cyg 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

  reply	other threads:[~2017-03-18 14:52 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-04  5:44 Daniel Santos
2017-03-04 11:27 ` Tim Prince via cygwin
2017-03-05  2:49 ` Daniel Santos
2017-03-05  3:49   ` JonY
2017-03-05  4:20     ` Daniel Santos
2017-03-05  7:23     ` Daniel Santos
2017-03-05  7:32     ` Daniel Santos
2017-03-05 11:08       ` David Billinghurst
2017-03-07  1:59         ` Daniel Santos
2017-03-07 13:58           ` cyg Simple
2017-03-07 23:21             ` Daniel Santos
2017-03-08  0:36               ` David Billinghurst
2017-03-08  5:14                 ` Daniel Santos
2017-03-08  8:21                   ` Brian Inglis
2017-03-09 22:48                     ` Daniel Santos
2017-03-09 23:51                       ` Brian Inglis
2017-03-10  0:01                         ` Tim Prince via cygwin
2017-03-10 18:56                         ` Achim Gratz
2017-03-10 20:30                           ` Brian Inglis
2017-03-10 20:48                             ` Achim Gratz
2017-03-13 16:35                           ` Daniel Santos
2017-03-13 17:25                             ` Marco Atzeri
2017-03-15 16:50                               ` Daniel Santos
2017-03-15 19:36                                 ` Brian Inglis
2017-03-16 20:55                                   ` Daniel Santos
2017-03-17  5:17                                     ` Brian Inglis
2017-03-18 13:48                                       ` Daniel Santos
2017-03-18 14:52                                         ` cyg Simple [this message]
2017-03-12  4:04                         ` Daniel Santos

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=a710962e-4ac0-2bfb-5dbc-3945e16543af@gmail.com \
    --to=cygsimple@gmail.com \
    --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).