From: Tatsuro MATSUOKA <tmacchant2@yahoo.co.jp>
To: Mark Geisert <mark@maxrnd.com>, <cygwin@cygwin.com>
Subject: Re: Patch request to qt 5.9.4
Date: Tue, 12 Mar 2019 08:26:00 -0000 [thread overview]
Message-ID: <68131193.416583.1552379148433.JavaMail.yahoo@mail.yahoo.co.jp> (raw)
In-Reply-To: <Pine.BSF.4.63.1903120059450.51174@m0.truegem.net>
----- Original Message -----
> From: Mark Geisert
> To: cygwin
> Cc:
> Date: 2019/3/12, Tue 17:04
> Subject: Re: Patch request to qt 5.9.4
>
> On Tue, 12 Mar 2019, Tatsuro MATSUOKA wrote:
> [...]
>>> From: Mark Geisert
>>> If it's not too much trouble, could you show what you tell gnuplot
> and how
>>> you
>>> set up the Qt environment? Are you running gnuplot from inside
> qterminal?
>>>
>>> ..mark
>> For qt graphics
>> gnuplot.exe uses driver process named gnuplot_qt.exe.
>>
>> gnuplot.exe tries connect with gnuplot_qt.exe
>> by
>>
>>
>> qt->socket.connectToServer(server);
>>
>>
>> in gnuplot.exe code but fails to connect with gnuplot_qt.exe.
>
> Yes, I understand that is happening at a low level. What exactly are you
> typing at your keyboard to make gnuplot produce the Qt graphics? I would
> like to reproduce your issue on my system; what do I need to do?
>
> Please refer to the specific questions I was asking above.
> Thank you,
>
> ..mark
Gnuplot distrubuted on Cyygwin does not link with Qt.
I am distrbuting develoment version of gnuplot with Qt (patched).
I have to prepare gnuplot binary without patch.
I have my web site and I will prepare binaries without stripped debug information
and upload on my web.
I will do it tomorrow morning. (Before job.)
Tatsuro
--
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:[~2019-03-12 8:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1439412702.1866573.1551653028041.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2019-03-03 22:43 ` Patch request to qt 5.9.4 (Re: [ANNOUNCEMENT] Qt 5.9.4) Tatsuro MATSUOKA
2019-03-04 16:32 ` Yaakov Selkowitz
2019-03-04 22:29 ` Tatsuro MATSUOKA
2019-03-05 12:57 ` Tatsuro MATSUOKA
2019-03-05 19:24 ` Achim Gratz
2019-03-05 23:58 ` Tatsuro MATSUOKA
2019-03-06 0:10 ` Tatsuro MATSUOKA
2019-03-06 1:10 ` Tatsuro MATSUOKA
2019-03-06 1:55 ` Tatsuro MATSUOKA
2019-03-06 2:25 ` Tatsuro MATSUOKA
2019-03-11 0:28 ` Tatsuro MATSUOKA
2019-03-11 0:50 ` Andrey Repin
2019-03-11 0:53 ` Yaakov Selkowitz
2019-03-11 3:33 ` Tatsuro MATSUOKA
2019-03-11 7:21 ` Mark Geisert
2019-03-11 7:56 ` Tatsuro MATSUOKA
2019-03-12 4:21 ` Mark Geisert
2019-03-12 6:51 ` Tatsuro MATSUOKA
2019-03-12 8:04 ` Patch request to qt 5.9.4 Mark Geisert
2019-03-12 8:26 ` Tatsuro MATSUOKA [this message]
2019-03-12 19:37 ` Achim Gratz
2019-03-12 23:22 ` Tatsuro MATSUOKA
2019-03-13 1:12 ` Mark Geisert
2019-03-13 4:27 ` Tatsuro MATSUOKA
2019-03-13 8:33 ` Mark Geisert
2019-03-15 8:06 ` Mark Geisert
2019-03-15 9:40 ` Tatsuro MATSUOKA
2019-03-16 0:41 ` Tatsuro MATSUOKA
2019-03-12 19:34 ` Achim Gratz
2019-03-11 9:45 ` Patch request to qt 5.9.4 (Re: [ANNOUNCEMENT] Qt 5.9.4) Corinna Vinschen
2019-03-12 4:16 ` Mark Geisert
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=68131193.416583.1552379148433.JavaMail.yahoo@mail.yahoo.co.jp \
--to=tmacchant2@yahoo.co.jp \
--cc=cygwin@cygwin.com \
--cc=mark@maxrnd.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).