From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: changes in 32-bit Cygwin OpenGL causing crashes?
Date: Wed, 25 May 2016 13:53:00 -0000 [thread overview]
Message-ID: <b643acbf-4a5b-3b24-103c-6838e6ee6a26@gmail.com> (raw)
In-Reply-To: <538382235.210794.1464156496492.JavaMail.yahoo@mail.yahoo.com>
On 25/05/2016 08: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.
>
> 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.
Feel free to propose a solution compatible with the
lack of dedicated man power.
The package per maintainer statistics can highlight
the workload issue:
2406 Yaakov Selkowitz
171 Jari Aalto
142 Achim Gratz
141 Marco Atzeri
82 Ken Brown
70 Dr. Volker Zell
44 Achim Gratz/Yaakov Selkowitz
39 Achim Gratz/Ken Brown
36 Corinna Vinschen
26 Andrew Schulman
22 Jonathan Yong
22 David Rothenberger
20 Eric Blake
19 Jon Turney
17 David Stacey
....
Total 3388
Of course not all the packages weight the same;
Jon and Corinna have very heavy loads
> 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.
Feel free to use the Time Machine
http://www.fruitbat.org/Cygwin/#cygwintimemachine
kindly provided by Peter
>
> 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
>
--
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:[~2016-05-25 9:28 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 [this message]
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=b643acbf-4a5b-3b24-103c-6838e6ee6a26@gmail.com \
--to=marco.atzeri@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).