From: Tatsuro MATSUOKA <tmacchant2@yahoo.co.jp>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] Updated: gnuplot-5.4.3-1
Date: Sat, 8 Jan 2022 15:34:54 +0900 (JST) [thread overview]
Message-ID: <1578215828.1163843.1641623694608.JavaMail.yahoo@mail.yahoo.co.jp> (raw)
In-Reply-To: <1578215828.1163843.1641623694608.JavaMail.yahoo.ref@mail.yahoo.co.jp>
> ----- Original Message -----
> Gnuplot version 5.4.3 is now available on Cygwin. The upstream release
> notes for this bugfix / minor feature enhancement release are available
> at:
>
> http://www.gnuplot.info/ReleaseNotes_5_4_3.html
>
>
> Cygwin Notes
> ============
>
> The tutorial has been removed from the 5.4 branch of gnuplot, so it is
> no longer available in the package.
>
> The ggi terminal has been dropped from the build. I am considering
> dropping both the gpic and the mif terminal in a further update as well.
>
> The wxt terminal is now available.
>
> The qt terminal still doesn't work on Cygwin due to either a Cygwin or
> Qt5 bug that is still under investigation. If you want to help, please
> install the gnuplot-qt5 package and try to debug it.
>
Attach the below patch to the qt-5.9.4
--- a/qtbase-everywhere-src-5.10.1/src/network/socket/qlocalsocket_unix.cpp
+++ b/qtbase-everywhere-src-5.10.1/src/network/socket/qlocalsocket_unix.cpp
@@ -239,7 +239,7 @@ void QLocalSocket::connectToServer(OpenM
}
// create the socket
- if (-1 == (d->connectingSocket = qt_safe_socket(PF_UNIX, SOCK_STREAM, 0,
O_NONBLOCK))) {
+ if (-1 == (d->connectingSocket = qt_safe_socket(PF_UNIX, SOCK_STREAM,
0))) {
d->errorOccurred(UnsupportedSocketOperationError,
QLatin1String("QLocalSocket::connectToServer"));
return;
I generaged renamed cygQt5Network-5.dll as cygQt5Network-5-gnuplot.dll and linked against it.
(Downgrade gcc-11 to gcc-10 is required for qt-5.9.4 build
https://cygwin.com/pipermail/cygwin/2021-December/250235.html)
The qt terminal works.
error messages are shown in interactive session.
For example,
terminal type is now 'qt'
gnuplot> pl x
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-user'
libGL error: Windows-DRI extension not available
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
gnuplot> QXcbShmImage: shmget() failed (88: Function not implemented) for size 1394424 (642x543)
For QStandardPaths error, the message is supressed if the environmental variable XDG_RUNTIME_DIR to
/tmp/runtime-user like
export XDG_RUNTIME_DIR=/tmp/runtime-user
For libGL errors, the messages are supressed if the environmental variable LIBGL_ALWAYS_INDIRECT to 1 like
export LIBGL_ALWAYS_INDIRECT=1
For QXcbShmImage: shmget() failed, the message is surpressed if cygserver service is running.
Right click terminal launcher and run as administrator and execute below
$ cygserver-config
/etc/cygserver.conf
is produced and then execute
$ cygrunsrv -S cygserver
Then cygserver service is registered to registry.
https://superuser.com/questions/738105/how-to-install-cygserver
Tatsuro
next parent reply other threads:[~2022-01-08 6:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1578215828.1163843.1641623694608.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2022-01-08 6:34 ` Tatsuro MATSUOKA [this message]
2022-01-07 16:20 Achim Gratz
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=1578215828.1163843.1641623694608.JavaMail.yahoo@mail.yahoo.co.jp \
--to=tmacchant2@yahoo.co.jp \
--cc=cygwin@cygwin.com \
--cc=matsuoka@nuce.nagoya-u.ac.jp \
/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).