Menu
▾
▴
gnuplot-beta
|
From: sfeam <sf...@us...> - 2017-08-28 16:53:37
|
We've had three release candidate for version 5.2 since May 2017 [*]. Four bugs have been found and fixed since -rc3, and a few bits of new code back-ported from 5.3. Does anyone see a need for an -rc5 before the final version 5.2 release? If not, I'll plan to package up a 5.2 source tarball at the end of this week. Ethan [*] actually four, but -rc4 changed only the Windows packaging. |
|
From: Tatsuro M. <tma...@ya...> - 2017-08-29 05:39:58
|
> From: sfeam via gnuplot-beta > To: gnuplot-beta > Cc: > Date: 2017/8/29, Tue 01:52 > Subject: Ready for final 5.2 release? > > We've had three release candidate for version 5.2 since May 2017 [*]. > Four bugs have been found and fixed since -rc3, and a few bits of new code > back-ported from 5.3. > > Does anyone see a need for an -rc5 before the final version 5.2 release? > > If not, I'll plan to package up a 5.2 source tarball at the end of this > week. > > Ethan In win/Readme-windows.txt, * wgnuplot.exe: GUI version and the default gnuplot executable. As of version 5 it emulates pipe functionality. As of version 5, it emulates pipe functionality. Now pipe works on also wgnuplot.exe, emulation is not used at present. The above sentence should be corrected accordingly. Tatsuro |
|
From: sfeam <sf...@us...> - 2017-08-29 06:36:00
|
On Tuesday, 29 August 2017 14:39:48 Tatsuro MATSUOKA wrote:
> > From: sfeam via gnuplot-beta
>
> > To: gnuplot-beta
> > Cc:
> > Date: 2017/8/29, Tue 01:52
> > Subject: Ready for final 5.2 release?
> >
> > We've had three release candidate for version 5.2 since May 2017 [*].
> > Four bugs have been found and fixed since -rc3, and a few bits of new code
> > back-ported from 5.3.
> >
> > Does anyone see a need for an -rc5 before the final version 5.2 release?
> >
> > If not, I'll plan to package up a 5.2 source tarball at the end of this
> > week.
> >
> > Ethan
>
> In win/Readme-windows.txt,
>
> * wgnuplot.exe: GUI version and the default gnuplot executable. As of version 5
> it emulates pipe functionality.
>
>
>
> As of version 5, it emulates pipe functionality.
>
> Now pipe works on also wgnuplot.exe, emulation is not used at present.
> The above sentence should be corrected accordingly.
>
> Tatsuro
>
In file config/mingw/Makefile I see
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
ifndef MINGW64
EXTRA_CPPFLAGS_PLAIN += -DUSE_FAKEPIPES
else
EXTRA_CPPFLAGS_PLAIN += -DPIPES
endif
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Does this mean that the 64-bit Mingw executable uses real pipes
but the 32-bit executable uses emulation?
Is it only true for Mingw?
Ethan
|
|
From: Tatsuro M. <tma...@ya...> - 2017-08-29 06:45:59
|
----- Original Message ----- > From: sfeam > To: Tatsuro MATSUOKA > Cc: gnu...@li...; bma...@we... > Date: 2017/8/29, Tue 15:34 > Subject: Re: Ready for final 5.2 release? > > On Tuesday, 29 August 2017 14:39:48 Tatsuro MATSUOKA wrote: >> > From: sfeam via gnuplot-beta >> >> > To: gnuplot-beta >> > Cc: >> > Date: 2017/8/29, Tue 01:52 >> > Subject: Ready for final 5.2 release? >> > >> > We've had three release candidate for version 5.2 since May 2017 > [*]. >> > Four bugs have been found and fixed since -rc3, and a few bits of new > code >> > back-ported from 5.3. >> > >> > Does anyone see a need for an -rc5 before the final version 5.2 > release? >> > >> > If not, I'll plan to package up a 5.2 source tarball at the end of > this >> > week. >> > >> > Ethan >> >> In win/Readme-windows.txt, >> >> * wgnuplot.exe: GUI version and the default gnuplot executable. As of > version 5 >> it emulates pipe functionality. >> >> >> >> As of version 5, it emulates pipe functionality. >> >> Now pipe works on also wgnuplot.exe, emulation is not used at present. >> The above sentence should be corrected accordingly. >> >> Tatsuro >> > > In file config/mingw/Makefile I see > > %%%%%%%%%%%%%%%%%%%%%%%%%%%%% > ifndef MINGW64 > EXTRA_CPPFLAGS_PLAIN += -DUSE_FAKEPIPES > else > EXTRA_CPPFLAGS_PLAIN += -DPIPES > endif > %%%%%%%%%%%%%%%%%%%%%%%%%%%%% > > Does this mean that the 64-bit Mingw executable uses real pipes > but the 32-bit executable uses emulation? > Is it only true for Mingw? > > Ethan MinGW 64 provides both 32 and 64 bit build tools. I have used it for both 32 and 64 bit binaries since 5.0.1. and 32 bit executable also does not use emulation. The pipe on wgnuplot is also currently supported on MSVC. See ChangeLog of 5.2-rc4 2017-07-29 Bastian Maerkisch <bma...@we...> * config/mingw/Makefile config/msvc/Makefile: Mingw-w64 and MSVC have working popen/pclose implementations for GUI applications. So we use them instead of our own "fake" pipe emulation. Bug #1950 Tatsuro |
|
From: Ethan A M. <sf...@us...> - 2017-08-29 22:27:28
|
On Tuesday, 29 August, 2017 14:39:48 Tatsuro MATSUOKA wrote: > > In win/Readme-windows.txt, > > * wgnuplot.exe: GUI version and the default gnuplot executable. As of version 5 > it emulates pipe functionality. > > Now pipe works on also wgnuplot.exe, emulation is not used at present. > The above sentence should be corrected accordingly. > > Tatsuro OK. I have updated that file. Please check that I understand correctly. There is no reason to mention wgnuplot_pipes at all, is this correct? The file now says gnuplot binaries ---------------- * wgnuplot.exe: GUI version and the default gnuplot executable. * gnuplot.exe: Text (console) mode version of the gnuplot executable with full pipe functionality as on other platforms. In contrast to wgnuplot.exe, this program can also accept commands on stdin (standard input) and print messages on stdout (standard output). It replaces a program pgnuplot.exe used by some earlier gnuplot versions. gnuplot.exe can be used as a graph engine by 3rd party applications like Octave (www.octave.org). * runtime library files Runtime library files (e.g. freetype6.dll) that are required for gnuplot are included in the package. Licenses of these runtime libraries can be found in the 'license' directory. Ethan |
|
From: Tatsuro M. <tma...@ya...> - 2017-08-30 02:02:20
|
> OK. I have updated that file. > Please check that I understand correctly. > There is no reason to mention wgnuplot_pipes at all, is this correct? Now the difference of wgnuplot_pipes from wgnuplot is to output stderr of child process or external libraries to the additional console. I myself agree with your description in which explanation of wgnuplot_pipes is just omitted but binary package keep to have it. > The file now says > > gnuplot binaries > ---------------- > > * wgnuplot.exe: GUI version and the default gnuplot executable. > > * gnuplot.exe: Text (console) mode version of the gnuplot executable with full > pipe functionality as on other platforms. In contrast to wgnuplot.exe, this > program can also accept commands on stdin (standard input) and print messages > on stdout (standard output). It replaces a program pgnuplot.exe used by some > earlier gnuplot versions. gnuplot.exe can be used as a graph engine by > 3rd party applications like Octave (www.octave.org). > > * runtime library files > Runtime library files (e.g. freetype6.dll) that are required for gnuplot > are included in the package. Licenses of these runtime libraries can be > found in the 'license' directory. > > > Runtime library files (e.g. freetype6.dll) small correction freetype6.dll is not used binary package distribution. Now the corresponding dll is named as libfreetype-6.dll. Tatsuro |
|
From: sfeam <sf...@us...> - 2017-08-30 04:03:08
|
On Wednesday, 30 August 2017 11:02:10 Tatsuro MATSUOKA wrote: > > OK. I have updated that file. > > > Please check that I understand correctly. > > There is no reason to mention wgnuplot_pipes at all, is this correct? > > > Now the difference of wgnuplot_pipes from wgnuplot is to output stderr of child process > or external libraries to the additional console. > > I myself agree with your description > > in which explanation of wgnuplot_pipes is just omitted but binary package keep to have it. > > > > > > The file now says > > > > gnuplot binaries > > ---------------- > > > > * wgnuplot.exe: GUI version and the default gnuplot executable. > > > > * gnuplot.exe: Text (console) mode version of the gnuplot executable with full > > pipe functionality as on other platforms. In contrast to wgnuplot.exe, this > > program can also accept commands on stdin (standard input) and print messages > > on stdout (standard output). It replaces a program pgnuplot.exe used by some > > earlier gnuplot versions. gnuplot.exe can be used as a graph engine by > > 3rd party applications like Octave (www.octave.org). > > > > * runtime library files > > Runtime library files (e.g. freetype6.dll) that are required for gnuplot > > are included in the package. Licenses of these runtime libraries can be > > found in the 'license' directory. > > > > > > > Runtime library files (e.g. freetype6.dll) > small correction > > freetype6.dll is not used binary package distribution. > Now the corresponding dll is named as libfreetype-6.dll. > > Tatsuro Got it. Thank you. Can you modify the Japanese version README-Windows-ja.txt the same way? Ethan |
|
From: Tatsuro M. <tma...@ya...> - 2017-08-30 04:33:58
|
----- Original Message ----- > From: sfeam > To: gnuplot-beta; Tatsuro MATSUOKA > Cc: bmaerkisch > Date: 2017/8/30, Wed 13:02 > Subject: Re: Ready for final 5.2 release? > > On Wednesday, 30 August 2017 11:02:10 Tatsuro MATSUOKA wrote: >> > OK. I have updated that file. >> >> > Please check that I understand correctly. >> > There is no reason to mention wgnuplot_pipes at all, is this correct? >> >> >> Now the difference of wgnuplot_pipes from wgnuplot is to output stderr of > child process >> or external libraries to the additional console. >> >> I myself agree with your description >> >> in which explanation of wgnuplot_pipes is just omitted but binary package > keep to have it. >> >> >> >> >> > The file now says >> > >> > gnuplot binaries >> > ---------------- >> > >> > * wgnuplot.exe: GUI version and the default gnuplot executable. >> > >> > * gnuplot.exe: Text (console) mode version of the gnuplot executable > with full >> > pipe functionality as on other platforms. In contrast to > wgnuplot.exe, this >> > program can also accept commands on stdin (standard input) and print > messages >> > on stdout (standard output). It replaces a program pgnuplot.exe used > by some >> > earlier gnuplot versions. gnuplot.exe can be used as a graph engine > by >> > 3rd party applications like Octave (www.octave.org). >> > >> > * runtime library files >> > Runtime library files (e.g. freetype6.dll) that are required for > gnuplot >> > are included in the package. Licenses of these runtime libraries > can be >> > found in the 'license' directory. >> > >> >> >> > > Runtime library files (e.g. freetype6.dll) >> small correction >> >> freetype6.dll is not used binary package distribution. >> Now the corresponding dll is named as libfreetype-6.dll. >> >> Tatsuro > > Got it. Thank you. > > Can you modify the Japanese version README-Windows-ja.txt > the same way? > > Ethan README-Windows-ja.txt has not been revised since 2016-03-07. I can revised it asap but it takes a bit time. In addition, this manuscript has been revised by Shigeharu Takeno so that the revised manuscript is better to reviewed by Shigeharu Takeno Tatsuro |
|
From: Mojca M. <moj...@gm...> - 2017-08-30 07:20:46
|
Dear Ethan, On 28 August 2017 at 18:52, sfeam via gnuplot-beta wrote: > We've had three release candidate for version 5.2 since May 2017 [*]. > Four bugs have been found and fixed since -rc3, and a few bits of new code > back-ported from 5.3. > > Does anyone see a need for an -rc5 before the final version 5.2 release? I tested the compilation on Mac now and I get a segmentation error (during compilation already). I didn't test previous RCs, so I cannot say since when this could be a problem. I'll try if I can figure out what causes it. Mojca |
|
From: Mojca M. <moj...@gm...> - 2017-08-30 07:46:02
|
On 30 August 2017 at 09:20, Mojca Miklavec wrote: > > I tested the compilation on Mac now and I get a segmentation error > (during compilation already). I didn't test previous RCs, so I cannot > say since when this could be a problem. > > I'll try if I can figure out what causes it. I'm sorry, this seems to be just a buggy default system compiler. (Everything sem ok after replacing the compiler with a newer one.) Mojca |
