Re: [Plplot-devel] NEW RELEASE?

[Alan W. I. <ir...@be...>]

Thanks, Geoffrey, for that java cookbook.  Rafael, if you cannot advise me
due to lack of java-Debian experience, the first thing I will try is to
install the dummy java Debian packages, and see what the documentation of
them says for making Debian work with the Blackdown version of the JDK.

As far as the python xw09.py segfault error, I know this did not occur for
my last tests in September.  But a lot has changed since then on my system
and also for plplot.  To help distinguish these two possibilities, can
anybody else replicate the bug for plplot HEAD and either or both of
python-1.5 and python-2.0?

Thanks.

Alan

email: ir...@be...
phone: 250-727-2902	FAX: 250-721-7715
snail-mail:
Dr. Alan W. Irwin
Department of Physics and Astronomy,
University of Victoria, P.O. Box 3055,
Victoria, British Columbia, Canada, V8W 3P6
__________________________

Linux-powered astrophysics
__________________________

On Fri, 19 Oct 2001, Geoffrey Furnish wrote:

> Alan W. Irwin writes:
>  > Geoffrey, I would be happy to add java to the testing, but I would need a
>  > short cookbook from you on exactly what software to get and what commands
>  > to run to exercise your examples.  I probably also need advice from Rafael
>  > about how to implement java on Debian.  For example, I looked for java
>  > packages, and there is dummy java virtual machine and dummy java compiler.
>  > The advice for these packages is to install them if you have a "real" java
>  > compiler and java virtual machine.  Huh?
>
> In order to compile the Java binding, you'll need a full JDK
> installed.  Our sysop did it here, so I haven't been through this
> personally for a while.  The definitive site for Java Linux, is
> blackdown.org, which ports Sun's JDK's to Linux.
.
.
.

> WRT python and plcont:  I remember that being a trouble spot.  I think
> if you read the plmodule.c code, you'll probably see the evidence of
> confused thrashing and milling about.  Sorry.  I thought I had left it
> in a useable state, but maybe not.  I /know/ that when I last ran
> pytkdemo, all the plots looked fine to me, but that's been a number of
> years/jobs ago, so my memory isn't 100%.  I hope I didn't have some
> uncommitted change/fix that got left on some disk N employers ago
> without ever getting check in...
>