gnuplot-beta

Finally: 4.0 tagged, tarred and ready to test.

[Hans-Bernhard B. <br...@ph...>]

Good news, everyone!

I've just concluded all the updates I could think of as having to be done
before the release (including updates to the Copyright years listed in
pretty much all the files), and tagged the current CVS status as the
GNUPLOT_RELEASE_4_0_0.  I'm uploading the prospective 4.0.0 source tarball
to private webspace of mine.  

  http://home.arcor.de/hans-bernhard.broeker/gnuplot-4.0.0.tar.gz

[There's a traffic limit on that, so please be gentle]

Unless I hear otherwise, this is the tarball that'll go out on
SourceForge.net by this time tomorrow (assuming Lars can sign it in time).

So: last-minute compilation and other tests should take place *now*.

Make sure that all the pieces needed for builds of binary packages are in
place.

I'll draft up an Announcement and send it round for checking, next.

-- 
Hans-Bernhard Broeker (br...@ph...)
Even if all the snow were burnt, ashes would remain.

Re: Finally: 4.0 tagged, tarred and ready to test.

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

On Tuesday 13 April 2004 11:24 am, Hans-Bernhard Broeker wrote:
>
> Unless I hear otherwise, this is the tarball that'll go out on
> SourceForge.net by this time tomorrow (assuming Lars can sign it in
> time).
>
> So: last-minute compilation and other tests should take place *now*.

The entry message  (and "show version") still report

   This is a pre-version of gnuplot 4.0. 
             ^^^^^^^^^^^     

Presumably once it's released it's no longer a "pre-version".



-- 
Ethan A Merritt       merritt@u.washington.edu
Biomolecular Structure Center
Mailstop 357742
University of Washington, Seattle, WA 98195

Re: Finally: 4.0 tagged, tarred and ready to test.

[Daniel J S. <dan...@ie...>]

Ethan Merritt wrote:

>On Tuesday 13 April 2004 11:24 am, Hans-Bernhard Broeker wrote:
>  
>
>>Unless I hear otherwise, this is the tarball that'll go out on
>>SourceForge.net by this time tomorrow (assuming Lars can sign it in
>>time).
>>
>>So: last-minute compilation and other tests should take place *now*.
>>    
>>
>
>The entry message  (and "show version") still report
>
>   This is a pre-version of gnuplot 4.0. 
>             ^^^^^^^^^^^     
>
>Presumably once it's released it's no longer a "pre-version".
>  
>

Also, if you are going to remove that portion of the start up message, 
the second last line might be modified for appearance.  The line "Send 
comments and requests for help to <gnu...@li...>" 
has a tab at the front, and with an 8 character tab common to many 
terminals (and an 80 character default width), that line becomes 83 
characters and extends to a new line in the next line's tab space. 
 Perhaps change that so it reads:

"Send comments and help requests to <gnu...@li...>"

and see if it works better.

Dan

non-critical problem...

[Daniel J S. <dan...@ie...>]

Rather than doing a full install, I built the latest tarball and decided 
to just test it within the "src" subdirectory.  I realize "you're not 
supposed to do that", but I ran across something a bit strange with the 
"gnuplot_x11" terminal.  Here is the message I get:

gnuplot> plot sin(x)
Expected X11 driver: /usr/local/libexec/gnuplot/4.0/gnuplot_x11
Exec failed: No such file or directory
See 'help x11' for more details

A couple things.  First, it might be nice if gnuplot would check the 
current active directory, i.e., the directory from which gnuplot is 
launched if it can't find gnuplot_x11 in the expected place.  For example,

Expected X11 driver: /usr/local/libexec/gnuplot/4.0/gnuplot_x11,
using ./gnuplot_x11 instead.

and if it isn't in the current working directory, state

Expected X11 driver: /usr/local/libexec/gnuplot/4.0/gnuplot_x11,
and none present in current working directory.
Exec failed: No such file or directory

If nobody likes that idea, fine.  However, the second thing is that 
after running gnuplot without "gnuplot_x11" present, the command line 
hung.  CNTRL-C broke from the hang, but afterward typing any keyboard 
keys no longer produces a response at the command line.  That may be a bug.

Dan

Re: non-critical problem...

[Lars H. <lhe...@us...>]

Daniel J Sebald writes:
> Rather than doing a full install, I built the latest tarball and decided 
> to just test it within the "src" subdirectory.  I realize "you're not 
> supposed to do that", but I ran across something a bit strange with the 
> "gnuplot_x11" terminal.  Here is the message I get:
> 
> gnuplot> plot sin(x)
> Expected X11 driver: /usr/local/libexec/gnuplot/4.0/gnuplot_x11
> Exec failed: No such file or directory
> See 'help x11' for more details
 
 See demo/Makefile.am.in, check-interactive target.

Re: Finally: 4.0 tagged, tarred and ready to test.

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

On Tuesday 13 April 2004 11:24 am, Hans-Bernhard Broeker wrote:
>
> So: last-minute compilation and other tests should take place *now*.

Building on Tru64 using DEC cc generates a large number of
compiler warnings due to the re-definition of TBOOLEAN.
But as far as I can tell the resulting code work OK.
So, not a show-stopper but it would be nice to have the build complete
with no compiler warnings.

jarlsberg [95] grep -i Warn make.log
cc: Warning: axis.c, line 188: In the definition of the function "axis_unlog_interval", the promoted type of checkrange is incompatible with the type of the corresponding parameter in a prior declaration.
cc: Warning: axis.c, line 747: In the definition of the function "round_outward", the promoted type of upwards is incompatible with the type of the corresponding parameter in a prior declaration.
cc: Warning: command.c, line 1034: In the definition of the function "print_set_output", the promoted type of append_p is incompatible with the type of the corresponding parameter in a prior declaration.
cc: Warning: contour.c, line 431: In the definition of the function "trace_contour", the promoted type of contr_isclosed is incompatible with the type of the corresponding parameter in a prior declaration.
cc: Warning: contour.c, line 843: In the definition of the function "put_contour", the promoted type of contr_isclosed is incompatible with the type of the corresponding parameter in a prior declaration.
cc: Warning: contour.c, line 890: In the definition of the function "chk_contour_kind", the promoted type of contr_isclosed is incompatible with the type of the corresponding parameter in a prior declaration.
cc: Warning: contour.c, line 919: In the definition of the function "put_contour_cubic", the promoted type of contr_isclosed is incompatible with the type of the corresponding parameter in a prior declaration.
cc: Warning: contour.c, line 1007: In the definition of the function "put_contour_bspline", the promoted type of contr_isclosed is incompatible with the type of the corresponding parameter in a prior declaration.
cc: Warning: contour.c, line 1067: In the definition of the function "gen_cubic_spline", the promoted type of contr_isclosed is incompatible with the type of the corresponding parameter in a prior declaration.
cc: Warning: contour.c, line 1365: In the definition of the function "gen_bspline_approx", the promoted type of contr_isclosed is incompatible with the type of the corresponding parameter in a prior declaration.
cc: Warning: contour.c, line 1436: In the definition of the function "eval_bspline", the promoted type of contr_isclosed is incompatible with the type of the corresponding parameter in a prior declaration.
cc: Warning: contour.c, line 1481: In the definition of the function "fetch_knot", the promoted type of contr_isclosed is incompatible with the type of the corresponding parameter in a prior declaration.
cc: Warning: hidden3d.c, line 517: In the definition of the function "store_vertex", the promoted type of color_from_column is incompatible with the type of the corresponding parameter in a prior declaration.
cc: Warning: misc.c, line 931: In the definition of the function "arrow_parse", the promoted type of allow_as is incompatible with the type of the corresponding parameter in a prior declaration.

[ and so on ....]


-- 
Ethan A Merritt       merritt@u.washington.edu
Biomolecular Structure Center
Mailstop 357742
University of Washington, Seattle, WA 98195

cygwin build report (was Re: Finally: 4.0 tagged, tarred and ready to test.)

[John A. T. <tu...@la...>]

Hans-Bernhard Broeker wrote:

> So: last-minute compilation and other tests should take place *now*.

ok, so unfortunately I don't have time to give a detailed report
right now, but can tomorrow (Wed.) afternoon

bottom line is that I ran into problems building and running
under cygwin - quick list of problems:

- couldn't get it to build with PDF support, even though PDFlib Lite
   is installed and I set --with-pdf=...

- went ahead and build w/o pdf, but interactive help isn't working
   (looks possibly related to line endings)

sorry I can't do more now - if whoever has been packaging up the
cygwin build doesn't see these problems, then maybe it's just
something I'm doing...

-John Turner

Re: cygwin build report (was Re: Finally: 4.0 tagged, tarred and ready to test.)

[Petr M. <mi...@ph...>]

Ok for OS/2 emx/gcc, and MSW Mingw, Cygwin/X11.

> bottom line is that I ran into problems building and running
> under cygwin - quick list of problems:
>
> - went ahead and build w/o pdf, but interactive help isn't working
>    (looks possibly related to line endings)

For me, it works.

If you experience problems with CRLFs, then look at cygwin's setup -- there
you configure this feature.

---
PM

Re: Finally: 4.0 tagged, tarred and ready to test.

[Petr M. <mi...@ph...>]

> So: last-minute compilation and other tests should take place *now*.

There is still the annoying Windows message:

		no HOME found

> I'll draft up an Announcement and send it round for checking, next.

I'll put it on web page too.


Binaries should be prepared then -- and some their README? -- and tested.


Aha, one question: Windows built by MingW should contain two binaries of
gnuplot:

1. wgnuplot.exe -- the "normal" one
2. wgnuplot????.exe -- like above but compiled with "PIPES=1" options
   to achieve unixish piping

Question: how to name this executable?
Candidates:
	wgnuplot2.exe
	wgnuplotp.exe
	wgnuplotu.exe
	wgnuplot_pipes.exe
	ugnuplot.exe
???
Note: pgnuplot.exe is already reserved.

---
PM