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 09:30:00 -0000	[thread overview]
Message-ID: <CANnLRdgB9nrJp2ZXKK3Bb_=RvnGsVepJaf3Ms2cNRAc0Ouc4eQ@mail.gmail.com> (raw)
In-Reply-To: <538382235.210794.1464156496492.JavaMail.yahoo@mail.yahoo.com>

On 25 May 2016 at 02:08,  <lloyd.wood@yahoo.co.uk> wrote:
>> 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.
>

dri-driver via LLVM is a hack on top of a hack on top of a hack as the
developer of the software will tell you. It works in the use cases he
develops for but outside of that you are very much all alone. So even
trying to have a 'known' good is hard for this because what worked on
your laptop/system may not work at all on any other one.

Heck it might not even work when the Windows OS underneath does an
update even though the hardware worked. To quote the road sign

Expect problems. Road construction ahead.

If you are needing better stability then you need to staff up
somewhere to have people to fix those problems.

> 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.
>
> Lloyd Wood
> http://savi.sf.net/
>
> --
> 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

  parent reply	other threads:[~2016-05-25 16:09 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
2016-05-25 16:05     ` Stephen John Smoogen
2016-05-25 13:53   ` Marco Atzeri
2016-05-26  9:30   ` Stephen John Smoogen [this message]
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='CANnLRdgB9nrJp2ZXKK3Bb_=RvnGsVepJaf3Ms2cNRAc0Ouc4eQ@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).