Re: [Plplot-devel] Java failures in building the Debian PLplot packages

[Rafael Laboissiere <rlaboiss@us...>]

* Alan W. Irwin <irwin@...> [2006-08-29 14:53]:

> On 2006-08-29 22:31+0200 Rafael Laboissiere wrote:
> 
> >The PLplot packages have just been kicked off Debian testing because they
> >are buggy.  In order to get the situation under control, I will take the
> >radical approach and drop the plplot-java package for all architectures.
> >I might reintroduce it in the future, once the Java problems are sorted
> >out.
> 
> Sounds like the right approach.

Indeed, the 5.6.1-8 version of the package built successfully for the
previously failing architectures.  This open the path for PLplot entering
Debian testing again.  Unfortunately, the Java bindings are gone.

> Once you have more time to look at this in detail, I suggest you pay
> close attention to exactly how your java build dependencies are being
> fulfilled on the failing architectures.  I think there is at least
> three different choices of free java tool chain, and your results will
> likely vary between them.

I only specify java-gcj-compat-dev, which is the correct way of
specifying the build-dependency, I have been told.

> On Debian stable, you may recall that gcj cannot build our java examples
> because we specify -encoding utf8 which is parsed okay by that old, buggy
> version of gcj, but which causes an internal error in that compiler. Other
> free java compilers (IIRC, kaffe) on Debian stable worked fine as did more
> modern versions of gcj.  That particular error is not relevant to the
> current problem except that it illustrates the point how results can vary
> between free java tool chains or different versions of the same java tool
> chain.

What is intriguing are the different reasons for failure in the different
architectures.  On arm, it fails with this error message:

=============================================================================
Making all in java
make[4]: Entering directory `/build/buildd/plplot-5.6.1/bindings/java'
if /bin/sh ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../include -I../../include  -I../../include  -I/usr/lib/jvm/java-gcj/include -I/usr/lib/jvm/java-gcj/include -I/usr/include/libgnomeprintui-2.2 -I/usr/include/libgnomeprint-2.2 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/libart-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/libpng12    -g -O2 -MT plplotjavac_wrap.lo -MD -MP -MF ".deps/plplotjavac_wrap.Tpo" -c -o plplotjavac_wrap.lo plplotjavac_wrap.c; \
	then mv -f ".deps/plplotjavac_wrap.Tpo" ".deps/plplotjavac_wrap.Plo"; else rm -f ".deps/plplotjavac_wrap.Tpo"; exit 1; fi
mkdir .libs
 gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../include -I../../include -I../../include -I/usr/lib/jvm/java-gcj/include -I/usr/lib/jvm/java-gcj/include -I/usr/include/libgnomeprintui-2.2 -I/usr/include/libgnomeprint-2.2 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/libart-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/libpng12 -g -O2 -MT plplotjavac_wrap.lo -MD -MP -MF .deps/plplotjavac_wrap.Tpo -c plplotjavac_wrap.c  -fPIC -DPIC -o .libs/plplotjavac_wrap.o
 gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../include -I../../include -I../../include -I/usr/lib/jvm/java-gcj/include -I/usr/lib/jvm/java-gcj/include -I/usr/include/libgnomeprintui-2.2 -I/usr/include/libgnomeprint-2.2 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/libart-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/libpng12 -g -O2 -MT plplotjavac_wrap.lo -MD -MP -MF .deps/plplotjavac_wrap.Tpo -c plplotjavac_wrap.c -o plplotjavac_wrap.o >/dev/null 2>&1
/bin/sh ../../libtool --tag=CC --mode=link gcc  -g -O2   -o plplotjavac_wrap.la -rpath /usr/lib/jni -rpath /usr/lib/jni -module -avoid-version -no-undefined ../../src/libplplotd.la plplotjavac_wrap.lo  -lm 
libtool: link: warning: `/usr/lib/gcc/arm-linux-gnu/4.1.2/../../..//libfreetype.la' seems to be moved
libtool: link: warning: `/usr/lib/gcc/arm-linux-gnu/4.1.2/../../..//libqhull.la' seems to be moved
libtool: link: warning: `/usr/lib/gcc/arm-linux-gnu/4.1.2/../../..//libltdl.la' seems to be moved
gcc -shared  .libs/plplotjavac_wrap.o  -Wl,--rpath -Wl,/build/buildd/plplot-5.6.1/src/.libs ../../src/.libs/libplplotd.so -L/usr/lib/gcc/arm-linux-gnu/4.1.2/../../../ -L/build/buildd/plplot-5.6.1/lib/csa/.libs -L/build/buildd/plplot-5.6.1/lib/nn/.libs -lm  -Wl,-soname -Wl,plplotjavac_wrap.so -o .libs/plplotjavac_wrap.so
ar cru .libs/plplotjavac_wrap.a  plplotjavac_wrap.o
ranlib .libs/plplotjavac_wrap.a
creating plplotjavac_wrap.la
(cd .libs && rm -f plplotjavac_wrap.la && ln -s ../plplotjavac_wrap.la plplotjavac_wrap.la)
javac   config.java -d . -classpath .
Exception in thread "main" java.lang.NoClassDefFoundError: org.eclipse.jdt.core.compiler.IProblem
   <<No stacktrace available>>
make[4]: *** [config.class] Error 1
make[4]: Leaving directory `/build/buildd/plplot-5.6.1/bindings/java'
=============================================================================

On hppa:

=============================================================================
Testing front-end java
PLplot library version: 5.6.1
./test_java.sh: line 47:   509 File size limit exceededjava -classpath ${javadir}:${PLPLOT_CLASSPATH} ${JAVA_TEST_OPTS} plplot.examples.x${index} -dev $device -o ${OUTPUT_DIR}/x${index}j.$dsuffix $options
./test_java.sh: line 47:   694 File size limit exceededjava -classpath ${javadir}:${PLPLOT_CLASSPATH} ${JAVA_TEST_OPTS} plplot.examples.x${index} -dev $device -o ${OUTPUT_DIR}/x${index}j.$dsuffix $options
./test_java.sh: line 47:   913 Bus error               java -classpath ${javadir}:${PLPLOT_CLASSPATH} ${JAVA_TEST_OPTS} plplot.examples.x${index} -dev $device -o ${OUTPUT_DIR}/x${index}j.$dsuffix $options
./test_java.sh: line 47:   916 Bus error               java -classpath ${javadir}:${PLPLOT_CLASSPATH} ${JAVA_TEST_OPTS} plplot.examples.x${index} -dev $device -o ${OUTPUT_DIR}/x${index}j.$dsuffix $options
./test_java.sh: line 47:   919 File size limit exceededjava -classpath ${javadir}:${PLPLOT_CLASSPATH} ${JAVA_TEST_OPTS} plplot.examples.x${index} -dev $device -o ${OUTPUT_DIR}/x${index}j.$dsuffix $options
Exception in thread "main" java.lang.NullPointerException
   at java.lang.Object.getClass(libgcj.so.7)
[...]
FAIL: plplot-test.sh
=============================================================================

I am puzzled.


-- 
Rafael

[Plplot-devel] Java failures in building the Debian PLplot packages

[Rafael Laboissiere <rlaboiss@us...>]

This request for help is directed to the PLplot Java gurus.

The PLplot Debian packages are failing for the hppa, sparc, and arm
architectures, apparently for different reasons but always related to Java
failures.  See the build logs can be seen at:

http://buildd.debian.org/fetch.php?&pkg=plplot&ver=5.6.1-7&arch=hppa&stamp=1155032156&file=log&as=raw
http://buildd.debian.org/fetch.php?&pkg=plplot&ver=5.6.1-7&arch=sparc&stamp=1156283997&file=log&as=raw
http://buildd.debian.org/fetch.php?&pkg=plplot&ver=5.6.1-7&arch=arm&stamp=1156329685&file=log&as=raw

Failure to build the package in any one of he supported architectures is
enough to get the package dropped form the distribution.  There has been
already a bug report targeted "serious" against the plplot package:

    http://bugs.debian.org/384329

This means that if I take no action the Debian (and Ubuntu as well as all
the Debian derivatives) will be deprived of our wonderful plotting library.
The actions that I can take are (1) fix the Java problems, (2) drop the
plplot-java package, or (3) drop the plplot-java package only for the
problematic architectures.

Solution (1) is beyond my reach.  Perhaps one of the PLplot Java gurus can
understanding (and fix) the bugs just from looking at the build logs above.

I am inclined to choose solution (2), because (3) would represent much
more work for me.  No other package in Debian depend on plplot-jave, so
this move would be safe.

Any help will be appreciated.

-- 
Rafael

Re: [Plplot-devel] Java failures in building the Debian PLplot packages

[Rafael Laboissiere <rlaboiss@us...>]

* Rafael Laboissiere <rlaboiss@...> [2006-08-28 19:16]:

> I am inclined to choose solution (2), because (3) would represent much
> more work for me.  No other package in Debian depend on plplot-jave, so
> this move would be safe.

The PLplot packages have just been kicked off Debian testing because they
are buggy.  In order to get the situation under control, I will take the
radical approach and drop the plplot-java package for all architectures.
I might reintroduce it in the future, once the Java problems are sorted
out.
 
-- 
Rafael

Re: [Plplot-devel] Java failures in building the Debian PLplot packages

[Alan W. Irwin <irwin@be...>]

On 2006-08-29 22:31+0200 Rafael Laboissiere wrote:

> * Rafael Laboissiere <rlaboiss@...> [2006-08-28 19:16]:
>
>> I am inclined to choose solution (2), because (3) would represent much
>> more work for me.  No other package in Debian depend on plplot-jave, so
>> this move would be safe.
>
> The PLplot packages have just been kicked off Debian testing because they
> are buggy.  In order to get the situation under control, I will take the
> radical approach and drop the plplot-java package for all architectures.
> I might reintroduce it in the future, once the Java problems are sorted
> out.

Sounds like the right approach.

Once you have more time to look at this in detail, I suggest you pay close
attention to exactly how your java build dependencies are being fulfilled on
the failing architectures.  I think there is at least three different choices
of free java tool chain, and your results will likely vary between them.

On Debian stable, you may recall that gcj cannot build our java examples
because we specify -encoding utf8 which is parsed okay by that old, buggy
version of gcj, but which causes an internal error in that compiler. Other
free java compilers (IIRC, kaffe) on Debian stable worked fine as did more
modern versions of gcj.  That particular error is not relevant to the
current problem except that it illustrates the point how results can vary
between free java tool chains or different versions of the same java tool
chain.

I have no idea which of the free java tool chains on Debian unstable are
considered most reliable at the moment, but it might be worth your while to
look closely at what other java-dependent packages do, and based on that be
much more specific in your build dependencies to force using the most
reliable java tool chain.

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); 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
(lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

Re: [Plplot-devel] Java failures in building the Debian PLplot packages

[Rafael Laboissiere <rlaboiss@us...>]

* Alan W. Irwin <irwin@...> [2006-08-29 14:53]:

> On 2006-08-29 22:31+0200 Rafael Laboissiere wrote:
> 
> >The PLplot packages have just been kicked off Debian testing because they
> >are buggy.  In order to get the situation under control, I will take the
> >radical approach and drop the plplot-java package for all architectures.
> >I might reintroduce it in the future, once the Java problems are sorted
> >out.
> 
> Sounds like the right approach.

Indeed, the 5.6.1-8 version of the package built successfully for the
previously failing architectures.  This open the path for PLplot entering
Debian testing again.  Unfortunately, the Java bindings are gone.

> Once you have more time to look at this in detail, I suggest you pay
> close attention to exactly how your java build dependencies are being
> fulfilled on the failing architectures.  I think there is at least
> three different choices of free java tool chain, and your results will
> likely vary between them.

I only specify java-gcj-compat-dev, which is the correct way of
specifying the build-dependency, I have been told.

> On Debian stable, you may recall that gcj cannot build our java examples
> because we specify -encoding utf8 which is parsed okay by that old, buggy
> version of gcj, but which causes an internal error in that compiler. Other
> free java compilers (IIRC, kaffe) on Debian stable worked fine as did more
> modern versions of gcj.  That particular error is not relevant to the
> current problem except that it illustrates the point how results can vary
> between free java tool chains or different versions of the same java tool
> chain.

What is intriguing are the different reasons for failure in the different
architectures.  On arm, it fails with this error message:

=============================================================================
Making all in java
make[4]: Entering directory `/build/buildd/plplot-5.6.1/bindings/java'
if /bin/sh ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../include -I../../include  -I../../include  -I/usr/lib/jvm/java-gcj/include -I/usr/lib/jvm/java-gcj/include -I/usr/include/libgnomeprintui-2.2 -I/usr/include/libgnomeprint-2.2 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/libart-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/libpng12    -g -O2 -MT plplotjavac_wrap.lo -MD -MP -MF ".deps/plplotjavac_wrap.Tpo" -c -o plplotjavac_wrap.lo plplotjavac_wrap.c; \
	then mv -f ".deps/plplotjavac_wrap.Tpo" ".deps/plplotjavac_wrap.Plo"; else rm -f ".deps/plplotjavac_wrap.Tpo"; exit 1; fi
mkdir .libs
 gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../include -I../../include -I../../include -I/usr/lib/jvm/java-gcj/include -I/usr/lib/jvm/java-gcj/include -I/usr/include/libgnomeprintui-2.2 -I/usr/include/libgnomeprint-2.2 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/libart-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/libpng12 -g -O2 -MT plplotjavac_wrap.lo -MD -MP -MF .deps/plplotjavac_wrap.Tpo -c plplotjavac_wrap.c  -fPIC -DPIC -o .libs/plplotjavac_wrap.o
 gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../include -I../../include -I../../include -I/usr/lib/jvm/java-gcj/include -I/usr/lib/jvm/java-gcj/include -I/usr/include/libgnomeprintui-2.2 -I/usr/include/libgnomeprint-2.2 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/libart-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/libpng12 -g -O2 -MT plplotjavac_wrap.lo -MD -MP -MF .deps/plplotjavac_wrap.Tpo -c plplotjavac_wrap.c -o plplotjavac_wrap.o >/dev/null 2>&1
/bin/sh ../../libtool --tag=CC --mode=link gcc  -g -O2   -o plplotjavac_wrap.la -rpath /usr/lib/jni -rpath /usr/lib/jni -module -avoid-version -no-undefined ../../src/libplplotd.la plplotjavac_wrap.lo  -lm 
libtool: link: warning: `/usr/lib/gcc/arm-linux-gnu/4.1.2/../../..//libfreetype.la' seems to be moved
libtool: link: warning: `/usr/lib/gcc/arm-linux-gnu/4.1.2/../../..//libqhull.la' seems to be moved
libtool: link: warning: `/usr/lib/gcc/arm-linux-gnu/4.1.2/../../..//libltdl.la' seems to be moved
gcc -shared  .libs/plplotjavac_wrap.o  -Wl,--rpath -Wl,/build/buildd/plplot-5.6.1/src/.libs ../../src/.libs/libplplotd.so -L/usr/lib/gcc/arm-linux-gnu/4.1.2/../../../ -L/build/buildd/plplot-5.6.1/lib/csa/.libs -L/build/buildd/plplot-5.6.1/lib/nn/.libs -lm  -Wl,-soname -Wl,plplotjavac_wrap.so -o .libs/plplotjavac_wrap.so
ar cru .libs/plplotjavac_wrap.a  plplotjavac_wrap.o
ranlib .libs/plplotjavac_wrap.a
creating plplotjavac_wrap.la
(cd .libs && rm -f plplotjavac_wrap.la && ln -s ../plplotjavac_wrap.la plplotjavac_wrap.la)
javac   config.java -d . -classpath .
Exception in thread "main" java.lang.NoClassDefFoundError: org.eclipse.jdt.core.compiler.IProblem
   <<No stacktrace available>>
make[4]: *** [config.class] Error 1
make[4]: Leaving directory `/build/buildd/plplot-5.6.1/bindings/java'
=============================================================================

On hppa:

=============================================================================
Testing front-end java
PLplot library version: 5.6.1
./test_java.sh: line 47:   509 File size limit exceededjava -classpath ${javadir}:${PLPLOT_CLASSPATH} ${JAVA_TEST_OPTS} plplot.examples.x${index} -dev $device -o ${OUTPUT_DIR}/x${index}j.$dsuffix $options
./test_java.sh: line 47:   694 File size limit exceededjava -classpath ${javadir}:${PLPLOT_CLASSPATH} ${JAVA_TEST_OPTS} plplot.examples.x${index} -dev $device -o ${OUTPUT_DIR}/x${index}j.$dsuffix $options
./test_java.sh: line 47:   913 Bus error               java -classpath ${javadir}:${PLPLOT_CLASSPATH} ${JAVA_TEST_OPTS} plplot.examples.x${index} -dev $device -o ${OUTPUT_DIR}/x${index}j.$dsuffix $options
./test_java.sh: line 47:   916 Bus error               java -classpath ${javadir}:${PLPLOT_CLASSPATH} ${JAVA_TEST_OPTS} plplot.examples.x${index} -dev $device -o ${OUTPUT_DIR}/x${index}j.$dsuffix $options
./test_java.sh: line 47:   919 File size limit exceededjava -classpath ${javadir}:${PLPLOT_CLASSPATH} ${JAVA_TEST_OPTS} plplot.examples.x${index} -dev $device -o ${OUTPUT_DIR}/x${index}j.$dsuffix $options
Exception in thread "main" java.lang.NullPointerException
   at java.lang.Object.getClass(libgcj.so.7)
[...]
FAIL: plplot-test.sh
=============================================================================

I am puzzled.


-- 
Rafael

Re: [Plplot-devel] Java failures in building the Debian PLplot packages

[Alan W. Irwin <irwin@be...>]

On 2006-08-30 08:50+0200 Rafael Laboissiere wrote:

> I only specify java-gcj-compat-dev, which is the correct way of
> specifying the build-dependency, I have been told.

I would double-check that, but if that is still the recommendation, then I
guess you had better stick to it.

>
>[...] What is intriguing are the different reasons for failure in the different
> architectures.  On arm, it fails with this error message: [...]
> javac   config.java -d . -classpath .
> Exception in thread "main" java.lang.NoClassDefFoundError: org.eclipse.jdt.core.compiler.IProblem
>   <<No stacktrace available>>

>
> On hppa:
>
> =============================================================================
> Testing front-end java
> PLplot library version: 5.6.1
> ./test_java.sh: line 47:   509 File size limit exceededjava -classpath ${javadir}:${PLPLOT_CLASSPATH} ${JAVA_TEST_OPTS} plplot.examples.x${index} -dev $device -o ${OUTPUT_DIR}/x${index}j.$dsuffix $options
> ./test_java.sh: line 47:   694 File size limit exceededjava -classpath ${javadir}:${PLPLOT_CLASSPATH} ${JAVA_TEST_OPTS} plplot.examples.x${index} -dev $device -o ${OUTPUT_DIR}/x${index}j.$dsuffix $options
> ./test_java.sh: line 47:   913 Bus error               java -classpath ${javadir}:${PLPLOT_CLASSPATH} ${JAVA_TEST_OPTS} plplot.examples.x${index} -dev $device -o ${OUTPUT_DIR}/x${index}j.$dsuffix $options
> ./test_java.sh: line 47:   916 Bus error               java -classpath ${javadir}:${PLPLOT_CLASSPATH} ${JAVA_TEST_OPTS} plplot.examples.x${index} -dev $device -o ${OUTPUT_DIR}/x${index}j.$dsuffix $options
> ./test_java.sh: line 47:   919 File size limit exceededjava -classpath ${javadir}:${PLPLOT_CLASSPATH} ${JAVA_TEST_OPTS} plplot.examples.x${index} -dev $device -o ${OUTPUT_DIR}/x${index}j.$dsuffix $options
> Exception in thread "main" java.lang.NullPointerException
>   at java.lang.Object.getClass(libgcj.so.7)
> [...]
> FAIL: plplot-test.sh
> =============================================================================
>
> I am puzzled.

So am I!  One thing you should do is to figure out exactly what "javac"
translates to on each of those platforms including version number of the
java compiler.  javac is determined through /etc/alternatives so it is
likely quite different on different platforms.  Also figure out what javac
means for the working ia32 platform.  If that version does not exist on the
the failing platforms, then you will probably want to exclude those
platforms at least until that working ia32 javac version exists on those
platforms.

It is always possible that some java change we made is introducing these
various javac errors, but I think it is more likely you are encountering
Debian free java tool chain problems.  I have had problems with those tool
chains even on the ia32 platform.  I mentioned gcj not working for the
Debian stable version, but working for later versions. I have also had some
bad experiences with non-gcj compilers as well.  My feeling is these free
java tool chain problems are largely gone for ia32, but I wouldn't be
surprised if they persist for other much less popular platforms.

Just out of curiosity do you always get the same javac error on a given
platform for every build attempt you have made in say the last six months or
did these various javac problems only start recently?

Alan
__________________________ 
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); 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
(lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

Re: [Plplot-devel] Java failures in building the Debian PLplot packages

[Rafael Laboissiere <rlaboiss@us...>]

* Alan W. Irwin <irwin@...> [2006-08-30 09:27]:

> So am I!  One thing you should do is to figure out exactly what "javac"
> translates to on each of those platforms including version number of the
> java compiler.  javac is determined through /etc/alternatives so it is
> likely quite different on different platforms.

I do not think so.  The autobuilders build the package from a clean
chroot and they all install gcj-4.1 as required (until version
5.6.1-7).  Your statement above is probably false.

> Also figure out what javac means for the working ia32 platform.

Which architecture is ia32?

> Just out of curiosity do you always get the same javac error on a given
> platform for every build attempt you have made in say the last six months or
> did these various javac problems only start recently?

The libplplot9-java package has been introduced in version 5.6.1-1. From
this version until version 5.6.1.-7, the package has never been autobuilt
correctly on any architecture due to dependency problems (see the details
in http://buildd.debian.org/build.php?pkg=plplot).  The only version with
Java building problems is 5.6.1-7.  The version 5.6.1-8 autobuilds
correctly, since the libplplot9-java package has been dropped.

-- 
Rafael

Re: [Plplot-devel] Java failures in building the Debian PLplot packages

[Alan W. Irwin <irwin@be...>]

On 2006-08-30 23:55+0200 Rafael Laboissiere wrote:

> Which architecture is ia32?

That is common notation for 32-bit intel compatible.

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); 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
(lbproject.sf.net).
__________________________

Linux-powered Science
__________________________