public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Stephen John Smoogen <smooge@gmail.com>
To: lloyd.wood@yahoo.co.uk, cygwin@cygwin.com
Subject: Re: changes in 32-bit Cygwin OpenGL causing crashes?
Date: Thu, 26 May 2016 06:54:00 -0000	[thread overview]
Message-ID: <CANnLRdijF5+o-TsrrOfrwHkayAT=fcFUkgeR8W_ZGw2cnNc3fA@mail.gmail.com> (raw)
In-Reply-To: <1568609610.213469.1464159398689.JavaMail.yahoo@mail.yahoo.com>

On 25 May 2016 at 02:56,  <lloyd.wood@yahoo.co.uk> wrote:
> http://www.redhat.com/services/custom/cygwin/support/
> OpenGL and drivers are not on the supported list.
>
> I suppose cygwin problems will all be moot once the
> Windows 10+Canonical Ubuntu is well-established, but we're not there yet.
> https://insights.ubuntu.com/2016/03/30/ubuntu-on-windows-the-ubuntu-userspace-for-windows-developers/
>

It will if you don't want to interact with the higher up Windows
system in many ways. The Ubuntu 'hack' is much more like you are
running a container of Linux on your Windows system so you can do
certain things inside that container, but interacting with the Windows
system is limited to what you can do. Now that might meet your needs
completely.

>
> Lloyd Wood
> http://savi.sf.net
>
> ----- Original Message -----
> From: Andrey Repin <anrdaemon@yandex.ru>
> To: lloyd.wood@yahoo.co.uk; cygwin@cygwin.com
> Sent: Wednesday, 25 May 2016, 16:39
> Subject: Re: changes in 32-bit Cygwin OpenGL causing crashes?
>
> Greetings, lloyd.wood@yahoo.co.uk!
>
>
>>> It seems still the same problem with dri-drivers
>>> https://sourceware.org/ml/cygwin/2016-04/msg00283.html
>>>
>>> probably caused by LLVM 3.7
>
>> Unfortunately, the dri-driver versions available in the installer
>> depend on LLVM 3.7, so, even though reverting back to LLVM 3.5
>> is offered when you select llvm, you can't pull in a dri-driver
>> that works with that older version of LLVM to test that hypothesis.
>> So, not much point to offering that older version of LLVM.
>
>> Regardless of the fact that OpenGL is broken (again), this is
>> really a problem with Cygwin as a perennial work-in-progress
>> and its (lack of) version control.
>
>> I'd like to be able to download a stable-known-to-work-on
>> a-specified date golden-master Cygwin, without incremental
>> upgrades, and revert to that known-to-work Cygwin if needs
>> be. Once every six months? I'd be good with that.
>
> RedHat offers paid support for Cygwin, you know.
>
> P.S.
> And it would be really wonderful, if you teach your mail client to not break
> threading.
>
>
> --
> With best regards,
> Andrey Repin
> Wednesday, May 25, 2016 09:38:43
>
> Sorry for my terrible english...
>
> --
> 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
>



-- 
Stephen J Smoogen.

--
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:[~2016-05-25 16:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <538382235.210794.1464156496492.JavaMail.yahoo.ref@mail.yahoo.com>
2016-05-25  9:37 ` lloyd.wood
2016-05-25  9:47   ` Andrey Repin
2016-05-25 10:07     ` lloyd.wood
2016-05-26  6:54       ` Stephen John Smoogen [this message]
2016-05-25 16:05     ` Stephen John Smoogen
2016-05-25 13:53   ` Marco Atzeri
2016-05-26  9:30   ` Stephen John Smoogen
2016-05-27  8:19     ` lloyd.wood
2016-05-27  9:37       ` Vince Rice
2016-05-27 19:35       ` Stephen John Smoogen
     [not found] <2026486348.2432030.1464050301698.JavaMail.yahoo.ref@mail.yahoo.com>
2016-05-24  0:41 ` lloyd.wood
2016-05-24  1:26   ` KIMURA Masaru
2016-05-24  9:14     ` marco atzeri
2016-05-25  6:59       ` KIMURA Masaru

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='CANnLRdijF5+o-TsrrOfrwHkayAT=fcFUkgeR8W_ZGw2cnNc3fA@mail.gmail.com' \
    --to=smooge@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=lloyd.wood@yahoo.co.uk \
    /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).