Re: Gnuplot version 5.0 is now available

[Ethan A M. <sf...@us...>]

On Tuesday, 06 January, 2015 19:25:17 Achim Gratz wrote:
> Ethan A Merritt writes:
> > Gnuplot version 5.0 is now available.
> 
> Thanks.  I've compiled on Cygwin (with cygport/autotools and both on
> 64bit and 32bit) and see the following issues:

Thanks for testing.

> 1. The Qt terminal still doesn't work.  No plot window ever shows up and
> each invocation of plot will produce another qt_terminal process.
> gnuplot itself seems to hang, but recovers after about 20s with a
> message about "font initialisation" taking too long.

I'm afraid I have no insight into what might be causing that problem.
IIRC the initial testers on OSX reported a similar problem but in
that case it really was font initialisation and the problem went 
away after the first run.

> 2. Configuring with Qt5 need changes to configure.in to work.  The
> configure script tries to determine the path to uic et.al. via a
> pkg-config query for exec_bin.  The correct variable to query is
> actually host_bins.

Hmm.
On my linux systems the host_bins field in Qt5Core.pc is empty,
so I am not sure this convention is universal.

On the other hand, the linux Qt5 package also sets the correct path via
/etc/profile.d/qt5.sh so that in practice the gnuplot autoconfigure
script would work anyhow.

Can you point to some documentation or policy about when that
pkg-config field is relevant or necessary?

> --8<---------------cut here---------------start------------->8---
>  QT5LOC=`$PKG_CONFIG --variable=exec_prefix Qt5Core`
>  UIC=${QT5LOC}/bin/uic
>  MOC=${QT5LOC}/bin/moc
>  RCC=${QT5LOC}/bin/rcc
>  LRELEASE=${QT5LOC}/bin/lrelease
> -------
>  QT5LOC=`$PKG_CONFIG --variable=host_bins Qt5Core`
>  UIC=${QT5LOC}/uic
>  MOC=${QT5LOC}/moc
>  RCC=${QT5LOC}/rcc
>  LRELEASE=${QT5LOC}/lrelease
> 
> --8<---------------cut here---------------end--------------->8---
> 
> 3. The demo plugin doesn't link, I haven't yet investigated why
> (probably some of the hardcoded linker flags don't make much sense on
> Cygwin).  I didn't find a way to tell configure that it should not
> compile the demo plugin other than removing the plugin support
> completely.

./configure --disable-plugins
is supposed to work.  Does it not?

> Other than that things seem to work well although we'll have to change a
> number of scripts that got caught in the changes w.r.t. to the linetype
> command and some tightened syntax rules.  On the upside it looks we can
> drop a patch that gave us more linetypes and dash patterns and just
> define them in the defaults instead.

If you don't mind my asking, who is the "we" in this case?

> 
> Regards,
> Achim.

	Ethan