From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: fltk does not work on cygwin version octave-6.4.0
Date: Tue, 21 Jun 2022 12:31:18 +0100 [thread overview]
Message-ID: <e9dc74d9-f4a9-0d57-2270-d84453c06764@dronecode.org.uk> (raw)
In-Reply-To: <20220621201800.4cf9fc45bfa42ed7fdadef59@nifty.ne.jp>
On 21/06/2022 12:18, Takashi Yano wrote:
> On Tue, 21 Jun 2022 19:48:09 +0900 (JST)
> Tatsuro MATSUOKA wrote:
>>> From: "Takashi Yano"
>>> To: "cygwin>
>> Cc: "Tatsuro MATSUOKA"
>>> Date: 2022/06/21 火 18:45
>>> Subject: Re: fltk does not work on cygwin version octave-6.4.0
>>
>>> On Tue, 21 Jun 2022 14:15:12 +0900 (JST)
>>> Tatsuro MATSUOKA wrote:
>>>> fltk does not work on cygwin version octave-6.4.0
>>>>
>>>> octave:1> graphics_toolkit fltk
>>>> octave:2> plot(1:10);
>>>> Insufficient GL support
>>>> error: unable to plot due to insufficient OpenGL support
>>>>
>>>> plot windows flashes and disappear immediately
>>>
[...]
>
> However, it works as expected, except that the following error message
> appears.
> libGL error: Windows-DRI extention disabled for GDI Generic renderer
>
> $ env LIBGL_ALWAYS_SOFTWARE=1 octave
> octave:1> graphics_toolkit fltk
> octave:2> plot(1:10);
>
> also works.
Unfortunately, LIBGL_ALWAYS_SOFTWARE doesn't behave the same everywhere,
since the set of GLX visuals available with it is based on those
available for direct rendering.
This seems similar to [1], which I made some changes in libGL to try to
address, but unfortunately that seems to never been resolved to a root
cause.
The "Insufficient GL support" message comes from octave, but since it
doesn't say what GL support it needs but thinks is missing, it's hard to
tell what the problem actually is.
I guess finding where that comes from in the octave source code would be
a good starting place.
[1] https://cygwin.com/pipermail/cygwin/2018-June/237659.html
next prev parent reply other threads:[~2022-06-21 11:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1014671988.1220984.1655788512175.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2022-06-21 5:15 ` Tatsuro MATSUOKA
2022-06-21 9:44 ` Takashi Yano
2022-06-21 10:48 ` Tatsuro MATSUOKA
2022-06-21 11:18 ` Takashi Yano
2022-06-21 11:25 ` Takashi Yano
2022-06-21 11:31 ` Jon Turney [this message]
2022-06-21 17:05 ` Marco Atzeri
2022-06-22 1:49 ` Tatsuro MATSUOKA
2022-06-22 3:53 ` Tatsuro MATSUOKA
2022-06-22 10:37 ` Tatsuro MATSUOKA
2022-06-22 19:33 ` Marco Atzeri
2022-06-22 23:05 ` Tatsuro MATSUOKA
2022-06-23 1:19 ` Marco Atzeri
2022-06-23 3:18 ` Tatsuro MATSUOKA
2022-06-26 13:58 ` Jon Turney
2022-06-27 3:23 ` Tatsuro MATSUOKA
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=e9dc74d9-f4a9-0d57-2270-d84453c06764@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).