public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "arrl via cygwin" <cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin alongside WSL
Date: Mon, 23 Oct 2017 14:57:00 -0000	[thread overview]
Message-ID: <11181830-a64e-38e7-4273-4af6a2bb1762@aol.com> (raw)
In-Reply-To: <1736415271.20171023170214@yandex.ru>



On 10/23/2017 10:02 AM, Andrey Repin wrote:
> Greetings, KARL BOTTS!
>
>> Does anybody have any concrete experience using Windows Subsystem for Linux
>> (hence WSL) on the same machine, alongside Cygwin?
> If you have any specific question - ask it.
> Asking a yes-or-no question doesn't add to the knowledge, and essentially
> boils down to "may I ask a question?"
> Yes, you may ask a question.
>
If you've watched gcc test results, you will have noticed that I have
been posting results for both cygwin and WSL since WSL first became
capable (occasionally) of running those tests.  My WSL results are
generally on an older box which is better able to run WSL than the newer
one, however it requires running external memory recovery more
frequently than cygwin does, and lately has been dying frequently anyway
in gfortran testsuite.    I haven't seen a feasible way to install WSL
other than with the Ubuntu.
Gcc attempts (unsuccessfully) to build and test cilkplus on WSL.  On
cygwin, there are major unsupported facilities (e.g. gstabs) which
produce hundreds of failures.  Although those 2 examples might
eventually be removed as being unworthy of support, it may be considered
that neither target is sufficiently popular with developers to see
support on the level of linux.

-- 
Tim Prince


--
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-10-23 14:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-23 12:38 KARL BOTTS
2017-10-23 14:05 ` Andrey Repin
2017-10-23 14:57   ` arrl via cygwin [this message]
2017-10-23 16:02 ` Brian Inglis
2017-10-24  7:34 ` Frank Fesevur
2017-10-24 19:47   ` Thomas Wolff
     [not found]     ` <331VJXVBf1952S01.1508878951@web01.cms.usa.net>
2017-10-24 21:04       ` KARL BOTTS
2017-10-24 17:57 ` Michael Enright
2017-10-24 22:20 Angelo Graziosi
2017-10-25  6:30 ` Thomas Wolff
2017-10-25 12:28   ` Angelo Graziosi
2017-10-25 17:27   ` Brian Inglis
2017-10-25 17:34     ` Thomas Wolff
2017-10-25 18:30     ` Brian Inglis
2017-10-25 21:18       ` Thomas Wolff
2017-10-26 16:13         ` Brian Inglis
2017-10-26 16:57           ` Brian Inglis
2017-10-26 22:11           ` Thomas Wolff
2017-10-31 18:11             ` Thomas Wolff
2017-11-02  3:19               ` Brian Inglis
2017-11-02 22:38                 ` Thomas Wolff
2017-11-03  5:15                   ` Brian Inglis

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=11181830-a64e-38e7-4273-4af6a2bb1762@aol.com \
    --to=cygwin@cygwin.com \
    --cc=n8tm@arrl.net \
    /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).