On 2004-02-12 09:19+0100 Rafael Laboissiere wrote:
> * Alan W. Irwin <irwin@...> [2004-02-11 18:32]:
> > On 2004-02-11 21:42+0100 Rafael Laboissiere wrote:
> > > There is a new CVS tarball available at the PLplot website:
> > >
> > > http://plplot.sourceforge.net/cvs-tarball/
> > >
> > > This is by no means a release candidate and it is not even minimally tested.
> > > I am making it available on Alan's request.
> > Thanks, Rafael. I have tested it now with my usual non-interactive tests.
> I forgot to tell that there is a simple way to test the tarball now:
> ./configure ; make check
> I just did it and the make check fails:
> Testing front-end tcl
> ./test_tcl.sh: line 27: /usr/local/bin/pltcl: No such file or directory
> ./test_tcl.sh: line 36: /usr/local/bin/pltcl: No such file or directory
> ./test_tcl.sh: line 45: /usr/local/bin/pltcl: No such file or directory
> FAIL: plplot-test.sh
> 1 of 1 tests failed
> Please report to plplot-devel@...
> This fails because test_tcl.sh assumes that PLplot is installed in the
> system. There are also problems with test_python.sh. I will fix these
I am glad your new testing scenario makes it easy for you and other
developers to test the build tree examples, and find the remaining bugs
there. As always, I have focussed my energies on testing the install tree
examples because that is the situation our rpm and deb users will be dealing
with. It is not quite as simple as cd $top-builddir/examples; make check,
but make install; cd $prefix/share/plplot$version/examples; make;
./plplot-test.sh is still pretty simple. As I said, that works well with
the current tarball.
> > There is a minor tcl name clash problem which I have now fixed in CVS, and
> > which only affects the output of example 1 for tcl in a minimal way for
> > those using this tarball.
> When I do a cvs update, I do not see this fix. Did you really cvs commit
Date: Wed, 11 Feb 2004 18:17:01 -0800
Subject: [Plplot-cvs] plplot/examples/tcl x14.tcl,1.6,1.7
Update of /cvsroot/plplot/plplot/examples/tcl
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv30838
Get rid of name clash between procs for this example and example 1. These
name clashes makes a difference when all these examples are sourced
same time (as occurs in tcldemos.tcl).
> Neither have I seen this:
> > Rafael's recent swig changes did screw up java. The fix (which I intend to
> > do) should be straightforward. It is simply a matter of getting #ifdef
> > tests done correctly for the java case. But for now avoid java problems
> > for this particular tarball by using the --disable-java option.
Straightforward does not mean it is going to be fast. There is lot's of
boring checking to do of your changes to make sure they are exactly
equivalent to the old system. This is manifestly not the case for Java
(since it is now broken), but it has to be double-checked for python as well
since not all python API is checked by the tests. I hope to finish these
checks this weekend.
> BTW, I would like to be able to test the java bindings, but I am not willing
> to install the non-free Blackdown Java Environment. Are there free
Rafael, it would be great if you would implement building the java examples
with gcj and adjust your Debian packages accordingly. There is direct
autotools support for gcj java builds. For those on the list that don't
know, gcj is a component of gcc that builds java source as a native
executable, and it is of course just as free as the rest of gcc. gcj does
not work at all well for the ancient gcc-2.9.5 compiler collection on my
Debian stable system, but you do have access to recent gcc versions so I am
pretty sure it will work quite nicely for you.
N.B. I would want you to preserve the exact current java system as a
distinct --enable-java option for those who don't have access to gcj, but
--enable-gcj-java could certainly be the default option that is mutually
exclusive with --enable-java.
Alan W. Irwin
Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).
Programming affiliations with the PLplot scientific plotting software
package (plplot.org), the Yorick front-end to PLplot (yplot.sf.net), the
Loads of Linux Links project (loll.sf.net), and the Linux Brochure Project