gnuplot-beta — Developers and beta testers of new gnuplot code

Re: Once more: Qt Terminal (no output)

[Philipp K. J. <ja...@ie...>]

On Sun, 15 Jun 2014 22:42:01 -0500
"Dmitri A. Sergatskov" <das...@gm...> wrote:

> On Sun, Jun 15, 2014 at 10:15 PM, Philipp K. Janert <ja...@ie...>
> wrote:
> 
> >
> > > >
> > > > Anything I should try to get more info?
> > > >
> > > >
> > > ​Could you send the output of
> > >
> > > ​
> > >  ldd /usr/local/bin/gnuplot
> > >
> > > ​(assuming this is where you install gnuplot)
> > >
> > > Dmitri.
> >
> > Below...
> >
> 
> ​OK, so Qt5 libraries linked in are:
> 
> ​    libQt5Network.so.5
> => /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 (0x00007f1dcdfc1000)
>     libQt5Gui.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
> (0x00007f1dcd9f4000)
>     libQt5Core.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
> (0x00007f1dcd3e0000)
> 
> --------------
> On my computer (Fedora 20) :
> 
>     libQt5Network.so.5 => /lib64/libQt5Network.so.5
> (0x00007fd50a499000) libQt5Svg.so.5 => /lib64/libQt5Svg.so.5
> (0x00007fd50a24a000) libQt5PrintSupport.so.5
> => /lib64/libQt5PrintSupport.so.5 (0x00007fd509fe4000)
>     libQt5Widgets.so.5 => /lib64/libQt5Widgets.so.5
> (0x00007fd509797000) libQt5Gui.so.5 => /lib64/libQt5Gui.so.5
> (0x00007fd509131000) libQt5Core.so.5 => /lib64/libQt5Core.so.5
> (0x00007fd508ace000)
> 
> 
> So your compile is missing few libraries.
> 
> Do you have libQt5Widgets.so.5 on your computer?
> (mine came in qt5-qtbase-gui-5.2.1-8 package)

Yes:
2013 /usr/lib/x86_64-linux-gnu/libQt5Widgets.so -> libQt5Widgets.so.5.0.2
2013 /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 -> libQt5Widgets.so.5.0.2
2013 /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.0 -> libQt5Widgets.so.5.0.2
2013 /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.0.2

> 
> Dmitri.
> --

Re: Once more: Qt Terminal (no output)

[Dmitri A. S. <das...@gm...>]

On Sun, Jun 15, 2014 at 10:15 PM, Philipp K. Janert <ja...@ie...> wrote:

>
> > >
> > > Anything I should try to get more info?
> > >
> > >
> > ​Could you send the output of
> >
> > ​
> >  ldd /usr/local/bin/gnuplot
> >
> > ​(assuming this is where you install gnuplot)
> >
> > Dmitri.
>
> Below...
>

​OK, so Qt5 libraries linked in are:

​    libQt5Network.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
(0x00007f1dcdfc1000)
    libQt5Gui.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
(0x00007f1dcd9f4000)
    libQt5Core.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
(0x00007f1dcd3e0000)

--------------
On my computer (Fedora 20) :

    libQt5Network.so.5 => /lib64/libQt5Network.so.5 (0x00007fd50a499000)
    libQt5Svg.so.5 => /lib64/libQt5Svg.so.5 (0x00007fd50a24a000)
    libQt5PrintSupport.so.5 => /lib64/libQt5PrintSupport.so.5
(0x00007fd509fe4000)
    libQt5Widgets.so.5 => /lib64/libQt5Widgets.so.5 (0x00007fd509797000)
    libQt5Gui.so.5 => /lib64/libQt5Gui.so.5 (0x00007fd509131000)
    libQt5Core.so.5 => /lib64/libQt5Core.so.5 (0x00007fd508ace000)


So your compile is missing few libraries.

Do you have libQt5Widgets.so.5 on your computer?
(mine came in qt5-qtbase-gui-5.2.1-8 package)

Dmitri.
--

Re: Once more: Qt Terminal (no output)

[Philipp K. J. <ja...@ie...>]

> >
> > Anything I should try to get more info?
> >
> >
> ​Could you send the output of
> 
> ​
>  ldd /usr/local/bin/gnuplot
> 
> ​(assuming this is where you install gnuplot)
> 
> Dmitri.

Below...


        linux-vdso.so.1 =>  (0x00007fffd51fe000)
        libreadline.so.6 => /lib/x86_64-linux-gnu/libreadline.so.6
        (0x00007f1dcfb52000) libgd.so.3
        => /usr/lib/x86_64-linux-gnu/libgd.so.3 (0x00007f1dcf8e7000)
        libwx_gtk2u_core-2.8.so.0
        => /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0
        (0x00007f1dcf305000) libwx_baseu-2.8.so.0
        => /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
        (0x00007f1dcefb9000) libpangocairo-1.0.so.0
        => /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0
        (0x00007f1dcedac000) libpango-1.0.so.0
        => /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
        (0x00007f1dceb5f000) libcairo.so.2
        => /usr/lib/x86_64-linux-gnu/libcairo.so.2 (0x00007f1dce856000)
        libgobject-2.0.so.0
        => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
        (0x00007f1dce605000) libglib-2.0.so.0
        => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007f1dce303000)
        libQt5Network.so.5
        => /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
        (0x00007f1dcdfc1000) libQt5Gui.so.5
        => /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
        (0x00007f1dcd9f4000) libQt5Core.so.5
        => /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
        (0x00007f1dcd3e0000) libdl.so.2
        => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f1dcd1dc000)
        libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
        (0x00007f1dcced8000) libm.so.6
        => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f1dccbd3000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
        (0x00007f1dcc9bd000) libpthread.so.0
        => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f1dcc7a0000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6
        (0x00007f1dcc3d7000) libtinfo.so.5
        => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x00007f1dcc1ae000)
        libjpeg.so.8 => /usr/lib/x86_64-linux-gnu/libjpeg.so.8
        (0x00007f1dcbf59000) libz.so.1
        => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f1dcbd3f000)
        libpng12.so.0 => /lib/x86_64-linux-gnu/libpng12.so.0
        (0x00007f1dcbb19000) libfreetype.so.6
        => /usr/lib/x86_64-linux-gnu/libfreetype.so.6
        (0x00007f1dcb877000) libfontconfig.so.1
        => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
        (0x00007f1dcb63a000) libXpm.so.4
        => /usr/lib/x86_64-linux-gnu/libXpm.so.4 (0x00007f1dcb428000)
        libvpx.so.1 => /usr/lib/x86_64-linux-gnu/libvpx.so.1
        (0x00007f1dcb194000) libtiff.so.5
        => /usr/lib/x86_64-linux-gnu/libtiff.so.5 (0x00007f1dcaf21000)
        libgtk-x11-2.0.so.0
        => /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
        (0x00007f1dca8e5000) libgdk-x11-2.0.so.0
        => /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
        (0x00007f1dca633000) libgdk_pixbuf-2.0.so.0
        => /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0
        (0x00007f1dca412000) libXinerama.so.1
        => /usr/lib/x86_64-linux-gnu/libXinerama.so.1
        (0x00007f1dca20f000) libXxf86vm.so.1
        => /usr/lib/x86_64-linux-gnu/libXxf86vm.so.1
        (0x00007f1dca009000) libSM.so.6
        => /usr/lib/x86_64-linux-gnu/libSM.so.6 (0x00007f1dc9e00000)
        libpangoft2-1.0.so.0
        => /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0
        (0x00007f1dc9beb000) libgmodule-2.0.so.0
        => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0
        (0x00007f1dc99e6000) libthai.so.0
        => /usr/lib/x86_64-linux-gnu/libthai.so.0 (0x00007f1dc97dd000)
        libpixman-1.so.0 => /usr/lib/x86_64-linux-gnu/libpixman-1.so.0
        (0x00007f1dc9534000) libxcb-shm.so.0
        => /usr/lib/x86_64-linux-gnu/libxcb-shm.so.0
        (0x00007f1dc9330000) libxcb-render.so.0
        => /usr/lib/x86_64-linux-gnu/libxcb-render.so.0
        (0x00007f1dc9127000) libxcb.so.1
        => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007f1dc8f09000)
        libXrender.so.1 => /usr/lib/x86_64-linux-gnu/libXrender.so.1
        (0x00007f1dc8cfe000) libX11.so.6
        => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007f1dc89c9000)
        libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6
        (0x00007f1dc87b7000) librt.so.1
        => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f1dc85ae000)
        libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6
        (0x00007f1dc83a6000) libpcre.so.3
        => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f1dc8167000)
        libGL.so.1 => /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
        (0x00007f1dc7f08000) libicui18n.so.48
        => /usr/lib/x86_64-linux-gnu/libicui18n.so.48
        (0x00007f1dc7b40000) libicuuc.so.48
        => /usr/lib/x86_64-linux-gnu/libicuuc.so.48
        (0x00007f1dc77d3000) /lib64/ld-linux-x86-64.so.2
        (0x00007f1dcfdb6000) libexpat.so.1
        => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007f1dc75a9000)
        liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5
        (0x00007f1dc7387000) libjbig.so.0
        => /usr/lib/x86_64-linux-gnu/libjbig.so.0 (0x00007f1dc7178000)
        libXfixes.so.3 => /usr/lib/x86_64-linux-gnu/libXfixes.so.3
        (0x00007f1dc6f72000) libatk-1.0.so.0
        => /usr/lib/x86_64-linux-gnu/libatk-1.0.so.0
        (0x00007f1dc6d50000) libgio-2.0.so.0
        => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
        (0x00007f1dc69ec000) libXi.so.6
        => /usr/lib/x86_64-linux-gnu/libXi.so.6 (0x00007f1dc67dc000)
        libXrandr.so.2 => /usr/lib/x86_64-linux-gnu/libXrandr.so.2
        (0x00007f1dc65d2000) libXcursor.so.1
        => /usr/lib/x86_64-linux-gnu/libXcursor.so.1
        (0x00007f1dc63c7000) libXcomposite.so.1
        => /usr/lib/x86_64-linux-gnu/libXcomposite.so.1
        (0x00007f1dc61c4000) libXdamage.so.1
        => /usr/lib/x86_64-linux-gnu/libXdamage.so.1
        (0x00007f1dc5fc1000) libICE.so.6
        => /usr/lib/x86_64-linux-gnu/libICE.so.6 (0x00007f1dc5da4000)
        libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1
        (0x00007f1dc5b9f000) libharfbuzz.so.0
        => /usr/lib/x86_64-linux-gnu/libharfbuzz.so.0
        (0x00007f1dc594c000) libdatrie.so.1
        => /usr/lib/x86_64-linux-gnu/libdatrie.so.1
        (0x00007f1dc5745000) libXau.so.6
        => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007f1dc5540000)
        libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6
        (0x00007f1dc533a000) libglapi.so.0
        => /usr/lib/x86_64-linux-gnu/libglapi.so.0 (0x00007f1dc5113000)
        libX11-xcb.so.1 => /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1
        (0x00007f1dc4f11000) libxcb-glx.so.0
        => /usr/lib/x86_64-linux-gnu/libxcb-glx.so.0
        (0x00007f1dc4cfa000) libxcb-dri2.so.0
        => /usr/lib/x86_64-linux-gnu/libxcb-dri2.so.0
        (0x00007f1dc4af5000) libdrm.so.2
        => /usr/lib/x86_64-linux-gnu/libdrm.so.2 (0x00007f1dc48e8000)
        libicudata.so.48 => /usr/lib/x86_64-linux-gnu/libicudata.so.48
        (0x00007f1dc3578000) libselinux.so.1
        => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007f1dc3355000)
        libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2
        (0x00007f1dc313b000) libgraphite2.so.3
        => /usr/lib/x86_64-linux-gnu/libgraphite2.so.3
        (0x00007f1dc2f20000)

Re: Once more: Qt Terminal (no output)

[Dmitri A. S. <das...@gm...>]

On Sun, Jun 15, 2014 at 8:18 PM, Philipp K. Janert <ja...@ie...> wrote:

>
>
> Anything I should try to get more info?
>
>
​Could you send the output of

​
 ldd /usr/local/bin/gnuplot

​(assuming this is where you install gnuplot)

Dmitri.
-- 
​

Re: Once more: Qt Terminal (no output)

[Philipp K. J. <ja...@ie...>]

On Sun, 15 Jun 2014 16:55:26 -0700
Ethan Merritt <merritt@u.washington.edu> wrote:

> On Sunday, 15 June 2014 04:47:14 PM Philipp K. Janert wrote:
> > 
> > I can now build and run gnuplot5 rc1 with Qt,
> > but when I try to use the qt terminal, I do
> > not get an output window. I also do not seem
> > to get an error message - just nothing happens.
> > 
> > I have no problem using either wxt or x11.
> > 
> > Is this known behavior?
> 
> Nope.
> 
> If you run "top" or "ps" in another terminal do you see gnuplot_qt?
> Do you see any evidence of font-config or some other system utility
> eating up time?

Both gnuplot and gnuplot_qt are running
(according to ps), but neither is consuming
significant resources (according to top).

My window manager is iceWM (for what it's
worth).

The gnuplot "output" is sent to "STDOUT".

"show terminal" says:
	terminal type is qt 0 font "Sans,9"

Anything I should try to get more info?

> 
> 	Ethan
> 

[snip]

Re: qt terminal on windows : pipe does not work

[Tatsuro M. <tma...@ya...>]

----- Original Message -----
> From: Tatsuro MATSUOKA 
> To: tmacchant3; gnuplot-beta
> Cc: 
> Date: 2014/6/14, Sat 11:47
> Subject: Re: qt terminal on windows : pipe does not work
 
> The bug is now fixed in CVS by Bastian.
> 
> 2014-06-13  Bastian Maerkisch   * 
> src/qtterminal/qt_term.cpp (qt_waitforinput):  Fix index error when trying to 
> stop thread which reads from pipe. Bug #1426
> I will update my binary distribution on Monday.
> Tatsuro


Done

http://www.tatsuromatsuoka.com/gnuplot/Eng/winbin/


Tatsuro

Re: Once more: Qt Terminal (no output)

[Ethan M. <merritt@u.washington.edu>]

On Sunday, 15 June 2014 04:47:14 PM Philipp K. Janert wrote:
> 
> I can now build and run gnuplot5 rc1 with Qt,
> but when I try to use the qt terminal, I do
> not get an output window. I also do not seem
> to get an error message - just nothing happens.
> 
> I have no problem using either wxt or x11.
> 
> Is this known behavior?

Nope.

If you run "top" or "ps" in another terminal do you see gnuplot_qt?
Do you see any evidence of font-config or some other system utility
eating up time?

	Ethan


> 
> 
> Here is the output from "show version long":
> 
>         G N U P L O T
>         Version 5.0 patchlevel rc1    last modified 2014-05-16 
> 
>         Copyright (C) 1986-1993, 1998, 2004, 2007-2014
>         Thomas Williams, Colin Kelley and many others
> 
>         gnuplot home:     http://www.gnuplot.info
>         mailing list:     gnu...@li...
>         faq, bugs, etc:   type "help FAQ"
>         immediate help:   type "help"  (plot window: hit 'h')
> Compile options:
> -READLINE  +LIBREADLINE  +HISTORY  
> -BACKWARDS_COMPATIBILITY  +BINARY_DATA  
> +GD_PNG  +GD_JPEG  +GD_TTF  +GD_GIF  +ANIMATION  
> -USE_CWDRC  +X11  +X11_POLYGON  +MULTIBYTE  +X11_EXTERNAL +USE_MOUSE
>         +HIDDEN3D_QUADTREE +DATASTRINGS  +HISTOGRAMS  +OBJECTS
>         +STRINGVARS  +MACROS  +THIN_SPLINES  +IMAGE  +USER_LINETYPES
>         +STATS +EXTERNAL_FUNCTIONS 
> 
> GNUPLOT_DRIVER_DIR =
> "/home/janert/Gnuplot-Workspace/gnuplot-5rc1/staging/libexec/gnuplot/5.0"
> GNUPLOT_PS_DIR     =
> "/home/janert/Gnuplot-Workspace/gnuplot-5rc1/staging/share/gnuplot/5.0/PostScript"
> HELPFILE           =
> "/home/janert/Gnuplot-Workspace/gnuplot-5rc1/staging/share/gnuplot/5.0/gnuplot.gih"
> 
> 
> ------------------------------------------------------------------------------
> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
> Find What Matters Most in Your Big Data with HPCC Systems
> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
> Leverages Graph Analysis for Fast Processing & Easy Data Exploration
> http://p.sf.net/sfu/hpccsystems
> _______________________________________________
> gnuplot-beta mailing list
> gnu...@li...
> Membership management via: https://lists.sourceforge.net/lists/listinfo/gnuplot-beta

-- 
mail:   Biomolecular Structure Center,  K-428 Health Sciences Bldg
        MS 357742,   University of Washington, Seattle 98195-7742

Once more: Qt Terminal (no output)

[Philipp K. J. <ja...@ie...>]

I can now build and run gnuplot5 rc1 with Qt,
but when I try to use the qt terminal, I do
not get an output window. I also do not seem
to get an error message - just nothing happens.

I have no problem using either wxt or x11.

Is this known behavior?


Here is the output from "show version long":

        G N U P L O T
        Version 5.0 patchlevel rc1    last modified 2014-05-16 

        Copyright (C) 1986-1993, 1998, 2004, 2007-2014
        Thomas Williams, Colin Kelley and many others

        gnuplot home:     http://www.gnuplot.info
        mailing list:     gnu...@li...
        faq, bugs, etc:   type "help FAQ"
        immediate help:   type "help"  (plot window: hit 'h')
Compile options:
-READLINE  +LIBREADLINE  +HISTORY  
-BACKWARDS_COMPATIBILITY  +BINARY_DATA  
+GD_PNG  +GD_JPEG  +GD_TTF  +GD_GIF  +ANIMATION  
-USE_CWDRC  +X11  +X11_POLYGON  +MULTIBYTE  +X11_EXTERNAL +USE_MOUSE
        +HIDDEN3D_QUADTREE +DATASTRINGS  +HISTOGRAMS  +OBJECTS
        +STRINGVARS  +MACROS  +THIN_SPLINES  +IMAGE  +USER_LINETYPES
        +STATS +EXTERNAL_FUNCTIONS 

GNUPLOT_DRIVER_DIR =
"/home/janert/Gnuplot-Workspace/gnuplot-5rc1/staging/libexec/gnuplot/5.0"
GNUPLOT_PS_DIR     =
"/home/janert/Gnuplot-Workspace/gnuplot-5rc1/staging/share/gnuplot/5.0/PostScript"
HELPFILE           =
"/home/janert/Gnuplot-Workspace/gnuplot-5rc1/staging/share/gnuplot/5.0/gnuplot.gih"

Re: Difficulties building rc1 with Qt on Linux

[Dmitri A. S. <das...@gm...>]

​​
​On Fedora 20 I had to add
​
LRELEASE=${QT5LOC}/bin/lrelease
​to configure.in
​

​otherwise I get
"lrelease: command not found" error during the make.​


​Dmitri.
-- 
​

Re: Difficulties building rc1 with Qt on Linux

[Philipp K. J. <ja...@ie...>]

[snip]

> 
> I don't know about Mint, but for Mageia lrelease comes in a 
> separate package qttools5-5.2.0-3.mga4

Ok, that did it. I needed to install:
	qttools5-dev-tools

I hadn't so far, because the package
description says "This package contains
the complete API documentation..." - 
which I understood to mean "ONLY the
documentation". 

I can compile now, many thanks.

Re: Difficulties building rc1 with Qt on Linux

[sfeam <sf...@us...>]

On Sunday, 15 June 2014 12:22:16 PM Philipp K. Janert wrote:
> 
> [snip]
> 
> > > 
> > > During the "configure" stage, everything goes
> > > fine, and configure tells me that the QT terminal
> > > will be built:
> > > 
> > >   Qt terminal: yes (qt5)
> > > 
> > > But then when I run "make", the process 
> > > eventually dies, with a complaint about the
> > > Qt utility "uic": 
> > > 
> > > /usr/bin/uic -o ui_QtGnuplotSettings.h
> > > qtterminal/QtGnuplotSettings.ui uic: could not find a Qt
> > > installation of '' 
> > > 
> > > The uic tool is installed (in /usr/bin/uic),
> > > but somehow the install seems to be broken -
> 
> Thanks for the quick response!
> 
> > 
> > What linux distro are you using?
> > Is Qt4 installed also?
> 
> The distro is Mint 16 on 64bit.
> 
> > 
> > At least on mine (Mageia4) the uic in /usr/bin/uic
> > is from Qt4, and the correct uic for Qt5 is in 
> > /usr/lib64/qt5/bin/uic
> 
> "locate" tells me that there is another "uic" in 
> /usr/lib/x86_64-linux-gnu/qt5/bin/ (of all places).
> 
> > 
> > The configure script requests the location of Qt5
> > executables via the pkg-config utility:
> > 
> >   pkg-config Qt5Core --variable=exec_prefix
> > 
> > If the pkg-config files for Qt5 are not present,
> > or are incorrect, that would explain your problem.
> > In this case please report the configuration error
> > to your linux distro.
> 
> The distro provides a "qt5-default" package (which
> I now have installed) and which (supposedly) makes
> Qt5 the default when dev libs are used, but it does
> not work (the prefix is still "/usr"). So that seems 
> to be a distro bug.
> 
> > 
> > Meanwhile you can probably work around this by finding
> > the line where this is invoked in the ./configure script:
> > 
> > [1] grep -n QT5LOC configure
> > 14304:      QT5LOC=`$PKG_CONFIG --variable=exec_prefix Qt5Core`
> > 
> > Change that to
> > 			QT5LOC=/usr/lib/qt5
> > 
> > or wherever Qt5 really is installed on your system.
> 
> That gets me further, but not home. Now, compilation 
> dies here:
> 
> lrelease qtterminal/po/qtgnuplot_fr.ts -qm qtgnuplot_fr.qm
> lrelease: could not exec '/usr/lib/x86_64-linux-gnu/qt5/bin/lrelease':
> No such file or directory
> 
> Which is odd in its own way, because lrelease seems
> to be only available (at least for my distro) in 
> some Qt4 package. 
> 
> Thoughts?

I don't know about Mint, but for Mageia lrelease comes in a 
separate package qttools5-5.2.0-3.mga4

	Ethan

Re: Difficulties building rc1 with Qt on Linux

[Philipp K. J. <ja...@ie...>]

On Sun, 15 Jun 2014 12:22:16 -0700
"Philipp K. Janert" <ja...@ie...> wrote:

Update: apparently, the qt5-default package
provided with my distro DOES work properly.
For instance, running uic -v at a regular cmd 
prompt now produces:
	Qt User Interface Compiler version 5.0.2
which seems quite reasonable. Apparently, the 
proper symlinks or whatever are being set in
the background.

Does this push the issue back to the "configure"
script? Why is "lrelease" even being invoked if
it is a Qt4 only tool? (There seems to be some
logic in "configure" that limits "lrelease" to 
Qt4 - for instance lines 14334-14339, but I do
not really understand what "configure" does.)

Best,

		Ph.



> 
> [snip]
> 
> > > 
> > > During the "configure" stage, everything goes
> > > fine, and configure tells me that the QT terminal
> > > will be built:
> > > 
> > >   Qt terminal: yes (qt5)
> > > 
> > > But then when I run "make", the process 
> > > eventually dies, with a complaint about the
> > > Qt utility "uic": 
> > > 
> > > /usr/bin/uic -o ui_QtGnuplotSettings.h
> > > qtterminal/QtGnuplotSettings.ui uic: could not find a Qt
> > > installation of '' 
> > > 
> > > The uic tool is installed (in /usr/bin/uic),
> > > but somehow the install seems to be broken -
> 
> Thanks for the quick response!
> 
> > 
> > What linux distro are you using?
> > Is Qt4 installed also?
> 
> The distro is Mint 16 on 64bit.
> 
> > 
> > At least on mine (Mageia4) the uic in /usr/bin/uic
> > is from Qt4, and the correct uic for Qt5 is in 
> > /usr/lib64/qt5/bin/uic
> 
> "locate" tells me that there is another "uic" in 
> /usr/lib/x86_64-linux-gnu/qt5/bin/ (of all places).
> 
> > 
> > The configure script requests the location of Qt5
> > executables via the pkg-config utility:
> > 
> >   pkg-config Qt5Core --variable=exec_prefix
> > 
> > If the pkg-config files for Qt5 are not present,
> > or are incorrect, that would explain your problem.
> > In this case please report the configuration error
> > to your linux distro.
> 
> The distro provides a "qt5-default" package (which
> I now have installed) and which (supposedly) makes
> Qt5 the default when dev libs are used, but it does
> not work (the prefix is still "/usr"). So that seems 
> to be a distro bug.
> 
> > 
> > Meanwhile you can probably work around this by finding
> > the line where this is invoked in the ./configure script:
> > 
> > [1] grep -n QT5LOC configure
> > 14304:      QT5LOC=`$PKG_CONFIG --variable=exec_prefix Qt5Core`
> > 
> > Change that to
> > 			QT5LOC=/usr/lib/qt5
> > 
> > or wherever Qt5 really is installed on your system.
> 
> That gets me further, but not home. Now, compilation 
> dies here:
> 
> lrelease qtterminal/po/qtgnuplot_fr.ts -qm qtgnuplot_fr.qm
> lrelease: could not exec '/usr/lib/x86_64-linux-gnu/qt5/bin/lrelease':
> No such file or directory
> 
> Which is odd in its own way, because lrelease seems
> to be only available (at least for my distro) in 
> some Qt4 package. 
> 
> Thoughts?
> 
> 
> ------------------------------------------------------------------------------
> HPCC Systems Open Source Big Data Platform from LexisNexis Risk
> Solutions Find What Matters Most in Your Big Data with HPCC Systems
> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
> Leverages Graph Analysis for Fast Processing & Easy Data Exploration
> http://p.sf.net/sfu/hpccsystems
> _______________________________________________
> gnuplot-beta mailing list
> gnu...@li...
> Membership management via:
> https://lists.sourceforge.net/lists/listinfo/gnuplot-beta

Re: Difficulties building rc1 with Qt on Linux

[Philipp K. J. <ja...@ie...>]

[snip]

> > 
> > During the "configure" stage, everything goes
> > fine, and configure tells me that the QT terminal
> > will be built:
> > 
> >   Qt terminal: yes (qt5)
> > 
> > But then when I run "make", the process 
> > eventually dies, with a complaint about the
> > Qt utility "uic": 
> > 
> > /usr/bin/uic -o ui_QtGnuplotSettings.h
> > qtterminal/QtGnuplotSettings.ui uic: could not find a Qt
> > installation of '' 
> > 
> > The uic tool is installed (in /usr/bin/uic),
> > but somehow the install seems to be broken -

Thanks for the quick response!

> 
> What linux distro are you using?
> Is Qt4 installed also?

The distro is Mint 16 on 64bit.

> 
> At least on mine (Mageia4) the uic in /usr/bin/uic
> is from Qt4, and the correct uic for Qt5 is in 
> /usr/lib64/qt5/bin/uic

"locate" tells me that there is another "uic" in 
/usr/lib/x86_64-linux-gnu/qt5/bin/ (of all places).

> 
> The configure script requests the location of Qt5
> executables via the pkg-config utility:
> 
>   pkg-config Qt5Core --variable=exec_prefix
> 
> If the pkg-config files for Qt5 are not present,
> or are incorrect, that would explain your problem.
> In this case please report the configuration error
> to your linux distro.

The distro provides a "qt5-default" package (which
I now have installed) and which (supposedly) makes
Qt5 the default when dev libs are used, but it does
not work (the prefix is still "/usr"). So that seems 
to be a distro bug.

> 
> Meanwhile you can probably work around this by finding
> the line where this is invoked in the ./configure script:
> 
> [1] grep -n QT5LOC configure
> 14304:      QT5LOC=`$PKG_CONFIG --variable=exec_prefix Qt5Core`
> 
> Change that to
> 			QT5LOC=/usr/lib/qt5
> 
> or wherever Qt5 really is installed on your system.

That gets me further, but not home. Now, compilation 
dies here:

lrelease qtterminal/po/qtgnuplot_fr.ts -qm qtgnuplot_fr.qm
lrelease: could not exec '/usr/lib/x86_64-linux-gnu/qt5/bin/lrelease':
No such file or directory

Which is odd in its own way, because lrelease seems
to be only available (at least for my distro) in 
some Qt4 package. 

Thoughts?

fit in 5.0-rc1 [was: Re: Gnuplot version 5 release candidate]

[Pieter-Tjerk de B. <p.t...@ut...>]

On Fri, Jun 06, 2014 at 11:03:52AM -0700, Ethan A Merritt wrote:

> > * The fit command in some cases interprets one column as errors, for
> >   compatibility with pre-5.0 versions, according to `help fit`.
> >   Perhaps it's an idea to change this, making 'noerror' the default,
> >   since 5.0 isn't supposed to be fully compatible anyway?
> >   That seems more systematic: then the error column is only there when
> >   explicitly indicated, and it makes the 'using' specification in case
> >   of 2 independent variables similar to what the user expects from splot.
> 
> I find myself somewhat by the new keywords also.
> The v5 docs appear contradictory. 

Hmm, indeed.

And there's more: it doesn't even describe the new `errors` keyword,
nor the new possibilities it offers (namely giving error estimates not
only for the dependent but also for the independent variables). The
rest of the text seems a bit confused; one sentence actually appears
twice in two different paragraphs ("there must be two more `using`
... one variable").

> which appears to say that "noerror" is _not_ the default, at least for the 3D 
> case.  Hence my confusion.  Do the keywords mean different things in 
> the 2D, 3D, and ND cases?

As far as I could find out, they mean the same.
Actually, "xerror", "yerror" and "zerror" are effectively all the same
as "errors z", only for different cases.

> For me the most useful statement in the v5 docs was that the "yerror"
> keyword made fit work analogously to "plot with yerrorbars".

Same for "xyerror" and "with xyerrorbars"; but "xerror" is _not_
analogous to "with xerrorbars".
In fact, I wonder whether it wouldn't be better to remove "xerror",
since it doesn't seem to have much purpose, and may be confusing.

While playing around with this, I also ran into a few bugs that
were due to variables not being properly reinitialized:
- repeatedly giving a command like:
    fit a*x+b 'tt.dat' u 1:2:3 errors x,z via a,b
  gives different error messages each time;
- the command:
    fit a*x+b 'tt.dat' u 1:2:3 errors x via a,b
  complains (rightfully) that z errors need to be given, but doesn't
  complain about it if one previously issued a fit command that _did_
  have z errors.

> Perhaps either the documentation or the keywords themselves could
> be made to match better with "plot/splot" commands?

Attached is a patch which makes the following changes:
- proper initialization of err_cols and num_errors; 
- noerror is now the default; this is incompatible with pre-5.0, but
  makes things more systematic (and match better with the splot command
  in case of 3D-fits);
- rewrite of the `fit` documentation, to match the new default meaning
  of the data columns, to explain the new errors options, and also to
  improve clarity on a few other aspects.

But of course, I don't know whether there is consensus about breaking
compatibility with pre-5.0 this way.

Regards,
  Pieter-Tjerk

Re: Difficulties building rc1 with Qt on Linux

[sfeam <sf...@us...>]

On Sunday, 15 June 2014 10:46:38 AM Philipp K. Janert wrote:
> 
> I am encountering difficulties building the rc1 
> with the Qt terminal.
> 
> During the "configure" stage, everything goes
> fine, and configure tells me that the QT terminal
> will be built:
> 
>   Qt terminal: yes (qt5)
> 
> But then when I run "make", the process 
> eventually dies, with a complaint about the
> Qt utility "uic": 
> 
> /usr/bin/uic -o ui_QtGnuplotSettings.h
> qtterminal/QtGnuplotSettings.ui uic: could not find a Qt installation
> of '' 
> 
> The uic tool is installed (in /usr/bin/uic),
> but somehow the install seems to be broken -

What linux distro are you using?
Is Qt4 installed also?

At least on mine (Mageia4) the uic in /usr/bin/uic
is from Qt4, and the correct uic for Qt5 is in 
/usr/lib64/qt5/bin/uic

The configure script requests the location of Qt5
executables via the pkg-config utility:

  pkg-config Qt5Core --variable=exec_prefix

If the pkg-config files for Qt5 are not present,
or are incorrect, that would explain your problem.
In this case please report the configuration error
to your linux distro.

Meanwhile you can probably work around this by finding
the line where this is invoked in the ./configure script:

[1] grep -n QT5LOC configure
14304:      QT5LOC=`$PKG_CONFIG --variable=exec_prefix Qt5Core`

Change that to
			QT5LOC=/usr/lib/qt5

or wherever Qt5 really is installed on your system.

> Apparently, it is more of a Qt problem, than a 
> gnuplot problem. Nevertheless is there a way to 
> either:
> - detect the problem during "configure"
> - fix the problem (better!)?

Probably the best is to get your distro to fix the
pkg-config support in their Qt5 development package.

Meanwhile the work-around above may get you going.

	cheers,

		Ethan

Difficulties building rc1 with Qt on Linux

[Philipp K. J. <ja...@ie...>]

I am encountering difficulties building the rc1 
with the Qt terminal.

During the "configure" stage, everything goes
fine, and configure tells me that the QT terminal
will be built:

  Qt terminal: yes (qt5)

But then when I run "make", the process 
eventually dies, with a complaint about the
Qt utility "uic": 

/usr/bin/uic -o ui_QtGnuplotSettings.h
qtterminal/QtGnuplotSettings.ui uic: could not find a Qt installation
of '' 

The uic tool is installed (in /usr/bin/uic),
but somehow the install seems to be broken -
when I run (at a shell prompt):

uic -v 

which should print the version number, I get
essentially the same error:

uic: could not find a Qt installation of ''

Apparently, it is more of a Qt problem, than a 
gnuplot problem. Nevertheless is there a way to 
either:
- detect the problem during "configure"
- fix the problem (better!)?

Best,

		Ph.


PS: It is absolutely AWESOME to see a
gnuplot 5.0 release candidate! Thanks
to everyone!

POSIX functions perhaps are deprecated for visual studio 2013 (was: isatty for windows)

[Tatsuro M. <tma...@ya...>]

----- Original Message -----

> From: Tatsuro MATSUOKA
> To: gnuplot-beta
> Cc: 
> Date: 2014/6/13, Fri 20:39
> Subject: isatty for windows
> 
> Hello
> 
> I have found that isatty is deprecated for visual studio 2013.
> http://msdn.microsoft.com/en-us/library/ms235388.aspx
> 
> 
> The page suggest to use _isatty instead.
> 
> The isatty function is used even in windows related codes.
> 
> This is mere information.
I found not only isatty but also fileno and getch are deprecated for visual studio 2013.
http://msdn.microsoft.com/en-us/library/ms235401.aspx

http://msdn.microsoft.com/en-us/library/ms235446.aspx


Perhaps POSIX functions are deprecated for visual studio 2013.
See :
http://stackoverflow.com/questions/814975/getch-is-deprecated


Tatsuro

Re: qt terminal on windows : pipe does not work

[Tatsuro M. <tma...@ya...>]

----- Original Message -----
> From: Tatsuro MATSUOKA
> To: tmacchant3 gnuplot-beta
> Cc: 
> Date: 2014/6/13, Fri 18:01
> Subject: Re: qt terminal on windows : pipe does not work
> 
> ----- Original Message -----
> 
>>  From: Tatsuro MATSUOKA 
>>  To: gnuplot-beta@
>>  Cc: 
>>  Date: 2014/6/13, Fri 13:03
>>  Subject: qt terminal on windows : pipe does not work
>> 
>>  Hello
>> 
>>  In the bug ticket[1],
>> 
>>  As I (Tatsuro MATSOKA) was shown, the issue on pipe feature does not work 
> on qt 
>>  terminal on windows.
>> 
>>  (For wxt and windows terminals, pipe works as expected. And on Ubuntu, pipe 
> 
>>  works on with the qt terminal.) .
>> 
>>  I do not have enough knowledge for qt terminal.
>> 
>>  If someone who has knowledge the qt terminal on windows, please commit the 
> bug 
>>  ticket [1].
>> 
>> 
>>  [1]
>>  #1426 pipes not working on MS Windows
>> 
>>  https://sourceforge.net/p/gnuplot/bugs/1426/
>> 
> 
> 
> As I wrote in the bug ticket that codes for windows of int qt_waitforinput(int 
> options) in qt_term.cpp should be revised for pipe to be accepted.



The bug is now fixed in CVS by Bastian.

2014-06-13  Bastian Maerkisch  <bma...@we...> * src/qtterminal/qt_term.cpp (qt_waitforinput):  Fix index error when trying to stop thread which reads from pipe. Bug #1426
I will update my binary distribution on Monday.
Tatsuro

isatty for windows

[Tatsuro M. <tma...@ya...>]

Hello

I have found that isatty is deprecated for visual studio 2013.
http://msdn.microsoft.com/en-us/library/ms235388.aspx


The page suggest to use _isatty instead.

The isatty function is used even in windows related codes.

This is mere information.

Tatsuro

Re: qt terminal on windows : pipe does not work

[Tatsuro M. <tma...@ya...>]

----- Original Message -----

> From: Tatsuro MATSUOKA 
> To: gnuplot-beta@
> Cc: 
> Date: 2014/6/13, Fri 13:03
> Subject: qt terminal on windows : pipe does not work
> 
> Hello
> 
> In the bug ticket[1],
> 
> As I (Tatsuro MATSOKA) was shown, the issue on pipe feature does not work on qt 
> terminal on windows.
> 
> (For wxt and windows terminals, pipe works as expected. And on Ubuntu, pipe 
> works on with the qt terminal.) .
> 
> I do not have enough knowledge for qt terminal.
> 
> If someone who has knowledge the qt terminal on windows, please commit the bug 
> ticket [1].
> 
> 
> [1]
> #1426 pipes not working on MS Windows
> 
> https://sourceforge.net/p/gnuplot/bugs/1426/
> 


As I wrote in the bug ticket that codes for windows of int qt_waitforinput(int options) in qt_term.cpp should be revised for pipe to be accepted.

Tatsuro

qt terminal on windows : pipe does not work

[Tatsuro M. <tma...@ya...>]

Hello

In the bug ticket[1],

As I (Tatsuro MATSOKA) was shown, the issue on pipe feature does not work on qt terminal on windows.

(For wxt and windows terminals, pipe works as expected. And on Ubuntu, pipe works on with the qt terminal.) .

I do not have enough knowledge for qt terminal.

If someone who has knowledge the qt terminal on windows, please commit the bug ticket [1].


[1]
#1426 pipes not working on MS Windows

https://sourceforge.net/p/gnuplot/bugs/1426/


Tatsuro

Re: about windows binaries

[Tatsuro M. <tma...@ya...>]

----- Original Message -----
> From: Tatsuro MATSUOKA 
> To: bmaerkisch; gnuplot-beta
> Cc: 
> Date: 2014/6/11, Wed 11:34
> Subject: Re: about  windows binaries
> 
> ----- Original Message -----
> 
>>  From: Bastian Märkisch 
>>  To: Tatsuro MATSUOKA ; gnuplot-beta
>>  Cc: 
>>  Date: 2014/6/10, Tue 20:34
>>  Subject: Re: about  windows binaries


<snip>


> 
> BTW, patch shown yesterday worked. (Yesterday I have mis-operated)
> I have posted to the patch ticket
> https://sourceforge.net/p/gnuplot/patches/693/
> 
> Please apply gnuplot.iss for qt terminal to work.
>  
Bastian


I have confirmed the fix to the cvs source. Thanks!

Tatsuro

Re: about windows binaries

[Tatsuro M. <tma...@ya...>]

----- Original Message -----

> From: Bastian Märkisch 
> To: Tatsuro MATSUOKA ; gnuplot-beta
> Cc: 
> Date: 2014/6/10, Tue 20:34
> Subject: Re: about  windows binaries
> 
> 
> Am 10.06.2014 12:49, schrieb Tatsuro MATSUOKA:
>>  ----- Original Message -----
>>>  From: Tatsuro MATSUOKA
> (snip)
>> 
>>  I also noticed that installer for 64 bit would like to install  
> "C:\Program Files (x86)".
>> 
>>  However, this should be "C:\Program Files" for 64 bit binary.
>> 
>>  I have a look at gnuplot.iss but I cannot find where should be modified.
>> 
> 
> You can find the required information here:
> http://www.jrsoftware.org/ishelp/topic_setup_architecturesinstallin64bitmode.htm
> 
> According to the docs, you should add following to the [Setup] section 
> (untested):
> 
>   ArchitecturesAllowed=x64
>   ArchitecturesInstallIn64BitMode=x64
> 
> Note that with these modifications the script can no longer be used for 32bit 
> installs.
> 
> 
> Since 32bit binaries run perfectly fine on 64bit Windows machines, I still fail 
> to see why 64bit binaries are worth the huge extra effort right now. The only 
> exception is the LFS support, but that can be handled differently, see 
> Ethan's patch #675.


Thanks. 

Adding 
   ArchitecturesAllowed=x64
   ArchitecturesInstallIn64BitMode=x64

makes installer work properly on 64 bit windows. (tested on win 7 and 8).
I will have the change as my local patch.

> Since 32bit binaries run perfectly fine on 64bit Windows machines, I still fail 

> to see why 64bit binaries are worth the huge extra effort right now. The only 
> exception is the LFS support, but that can be handled differently, see 
> Ethan's patch #675.


You are correct. 
But now Cygwin works both 32 bit and 64 bit. 
The 64 bit gnuplot binary works on Cygwin x86_64.
I think that the existence of 64 bit binary for 64 bit platform is natural.
Once 64 bit binaries can be build, it is not so difficult to work further.

BTW, patch shown yesterday worked. (Yesterday I have mis-operated)
I have posted to the patch ticket
https://sourceforge.net/p/gnuplot/patches/693/



Please apply gnuplot.iss for qt terminal to work.
 
Tatsuro

Re: about windows binaries

[Bastian M. <bma...@we...>]

Am 10.06.2014 12:49, schrieb Tatsuro MATSUOKA:
> ----- Original Message -----
>> From: Tatsuro MATSUOKA
(snip)
>
> I also noticed that installer for 64 bit would like to install   "C:\Program Files (x86)".
>
> However, this should be "C:\Program Files" for 64 bit binary.
>
> I have a look at gnuplot.iss but I cannot find where should be modified.
>

You can find the required information here:
http://www.jrsoftware.org/ishelp/topic_setup_architecturesinstallin64bitmode.htm

According to the docs, you should add following to the [Setup] section 
(untested):

   ArchitecturesAllowed=x64
   ArchitecturesInstallIn64BitMode=x64

Note that with these modifications the script can no longer be used for 
32bit installs.


Since 32bit binaries run perfectly fine on 64bit Windows machines, I 
still fail to see why 64bit binaries are worth the huge extra effort 
right now. The only exception is the LFS support, but that can be 
handled differently, see Ethan's patch #675.

   Bastian

>
> Please make appropriate changes to the matters above.
>
> Tatsuro
>

Re: about windows binaries

[Tatsuro M. <tma...@ya...>]

----- Original Message -----
> From: Tatsuro MATSUOKA 
> Hello
> 
> http://www.tatsuromatsuoka.com/gnuplot/Eng/winbin/
> 
> 
> 3. I have found that qt terminal does not work when loading gnuplot_qt.exe when 
> my binary installed into PC in which qt binary is not installed. The error 
> dialogs are
> http://www.geocities.jp/tmgpltwin/Files/Files.html#0060
> 
> 20140610_qtlog.png, 20140610_qtlog2.png
> 
> 
> The binary packages include 
>  Qt5Core.dll, Qt5Gui.dll, Qt5Network.dll, Qt5PrintSupport.dll, Qt5Svg.dll, 
> and Qt5Widgets.dll as dynamic link files.  I have checked the dependency dll 
> files for gnuplot_qt.exe using the dependency walker. However, the described dll 
> files seem to be enough from the dependency walker analysis. 
> If someone knows additional dll files for Qt terminal to work on windows PC in 
> which Qt binary is not installed, please let me know. 
> 


Akira Kakuto kindly told me that install plugins/platforms/qwindows.dll as bin/platforms/qwindows.dll.

I tested it and confirmed that worked.
I have written a small patch to gnuplot.iss to include bin/platforms/qwindows.dll.


--- a/win/gnuplot.iss2014-06-01 18:28:57 +0900
+++ b/win/gnuplot.iss2014-06-10 18:54:34 +0900
@@ -118,6 +118,7 @@
 Source: "bin\gnuplot_qt.exe"; DestDir: "{app}\bin\"; Flags: skipifsourcedoesntexist ignoreversion; Components: core
 ; core support files
 Source: "bin\*.dll"; DestDir: "{app}\bin\"; Flags: skipifsourcedoesntexist ignoreversion; Components: core
+Source: "bin\platforms\qwindows.dll"; DestDir: "{app}\bin\platforms"; Flags: skipifsourcedoesntexist ignoreversion; Components: core
 Source: "bin\wgnuplot.mnu"; DestDir: {app}\bin\; Components: core
 Source: "bin\wgnuplot.chm"; DestDir: {app}\bin\; Components: core
 Source: "share\*"; DestDir: {app}\share\; Flags: recursesubdirs; Components: core


I also noticed that installer for 64 bit would like to install   "C:\Program Files (x86)".

However, this should be "C:\Program Files" for 64 bit binary.

I have a look at gnuplot.iss but I cannot find where should be modified.


Please make appropriate changes to the matters above.

Tatsuro