public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Stephen John Smoogen <smooge@gmail.com>
To: lloyd.wood@yahoo.co.uk
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: changes in 32-bit Cygwin OpenGL causing crashes?
Date: Fri, 27 May 2016 19:35:00 -0000	[thread overview]
Message-ID: <CANnLRdgYt7zzw=Qx2jyG9qUOD3WT5ihMMLi7CSvb5Et4VUadCg@mail.gmail.com> (raw)
In-Reply-To: <1871468680.106497.1464318087251.JavaMail.yahoo@mail.yahoo.com>

On 26 May 2016 at 23:01,  <lloyd.wood@yahoo.co.uk> wrote:
> It's odd, the amount of extra support that Cygwin needs.
>
> Okay, OpenGL is broken in 32-bit cygwin, not for the first
> time.
>

It is broken a lot upstream also. 32 bit is considered a "if we can
get to it we will do so, but no promises" by various developers. The
llvm dri is also a 'if it works fine, if it doesn't we will get to it
when we can'. Also all of those problems are not stuff that Cygwin can
fix and need to be reported and dealt with upstream first. The
upstream developer works very hard on some specific hardware that he
knows he can support and if you have the hardware and such that is
needed, it works great. If it doesn't, he looks for people to help out
and fix those areas and will try to fix it but can not


> Those are the major things that come to mind when I think
> of Cygwin.
>
> Notes at:
> http://sat-net.com/L.Wood/software/SaVi/building-under-Windows/
>
> where I try and suggest to users that Cygwin is not
> their best choice. Really.
>

Thank you for your time and input. Good day.


-- 
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-27 15:00 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
2016-05-27  8:19     ` lloyd.wood
2016-05-27  9:37       ` Vince Rice
2016-05-27 19:35       ` Stephen John Smoogen [this message]
     [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='CANnLRdgYt7zzw=Qx2jyG9qUOD3WT5ihMMLi7CSvb5Et4VUadCg@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).