You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Andrew McIntyre <mc...@gmail.com> on 2005/07/13 08:14:49 UTC
Re: derby-split-2 (was: BATCH: All dressed up, with nowhere to go...)
Sorry for the delay here...
On Jul 11, 2005, at 4:46 AM, gump@vmgump.apache.org wrote:
> Dear Gumpmeisters,
>
> The following 11 notifys should have been sent
>
> *********************************************************** G U M P
> [GUMP@vmgump]: Project derby-split-2 (in module db-derby) failed
> *********************************************************** G U M P
> <snip lots of gumping>
> *********************************************************** G U M P
> [GUMP@vmgump]: Project derby-split-2 (in module db-derby) failed
> To whom it may engage...
> Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/
> local/gump/public/workspace/xml-commons/java/external/build/xml-
> apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/
> xercesImpl.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/
> public/gump/work/merge.xml -Ddeprecation=false -
> Dbuild.sysclasspath=last -Dempty=/usr/local/gump/packages/java-
> runtime-1.3/rt.jar -Dbuild.compiler=jikes gump_split_2
> [Working Directory: /usr/local/gump/public/workspace/db-derby]
> CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/
> workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/
> ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/
> dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/
> ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/
> lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-
> launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-
> nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/
> usr/local/gump/public/workspace/jakarta-servletapi-5/jsr154/dist/
> lib/servlet-api.jar:/usr/local/gump/public/workspace/jakarta-oro/
> jakarta-oro-11072005.jar:/usr/local/gump/packages/javacc-3.1/bin/
> lib/javacc.jar:/usr/local/gump/packages/java-runtime-1.3/rt.jar:/
> usr/local/gump/packages/jce/jce-jdk13-116.jar:/usr/local/gump/
> packages/jdbc2_0/jdbc2_0-stdext.jar:/usr/local/gump/packages/jta-
> spec1_0_1/jta-spec1_0_1.jar
> ---------------------------------------------
> [javac] 46. public class BrokeredConnection implements
> Connection
> [javac] ^----------------^
> [javac] *** Semantic Error: The abstract method "void rollback
> (java.sql.Savepoint $1) throws java.sql.SQLException;", inherited
> from type "java.sql.Connection", is not implemented in the non-
> abstract class "org.apache.derby.iapi.jdbc.BrokeredConnection".
This, and the other failures in derby-split-2, would appear to be the
result of JDK 1.4 interfaces being on the classpath before the JDK
1.3 interfaces against which these specific classes are expected to
be compiled.
However, the classpath reported by Gump doesn't appear to have any
JDK 1.4 classes on it, besides tools.jar. Also, I had a script which
emulates the Derby build in Gump by building with just one JDK on the
classpath for each split, and this script still compiles Derby
successfully. Is it possible that a change to Gump (or Ant) was made
that is causing JDK 1.4 (or higher) classes to appear on the
compilation classpath before the JDK 1.3 classes which are needed for
this compile?
I realize there's a lot of change to Gump going on right now, but I
thought I should at least let you know that this specific failure
hadn't gone completely unnoticed. Please let me know if there's
anything I can do to help resolve this problem.
Thanks,
andrew
Re: derby-split-2
Posted by Stefan Bodewig <bo...@apache.org>.
On Wed, 13 Jul 2005, Leo Simons <ma...@leosimons.com> wrote:
> which obviously means that's the rt.jar from the 1.4 jre that I
> linked to, probably because I couldn't figure out some build
> failure.
So I'll better fix that 8-)
>> I vaguely recall we've been running our own version of Jikes on
>> brutus while the one on vmgump is a stock debian installed one.
>
> I know I didn't install jikes. Nothing mentioned about it on
> http://wiki.apache.org/gump/VmgumpConfig. If we had a custom jikes
> on brutus it wasn't in /opt.
I think Dims compiled it from scratch since the Debian version had
some bugs that caused trouble in the Kaffe builds.
> Regardless of what you change, please update the wiki page :-)
Will do.
> You may have noticed I'm working on some sane management of
> installed packages for gump3. Will make sure that this kind of thing
> is a lot easier to debug than it is now.
So true.
Thanks
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: derby-split-2
Posted by Leo Simons <ma...@leosimons.com>.
Stefan Bodewig wrote:
> On Tue, 12 Jul 2005, Andrew McIntyre <mc...@gmail.com> wrote:
>>Sorry for the delay here...
>
> I've been meaning to look into it myself but never found the time,
> sorry.
>
>>However, the classpath reported by Gump doesn't appear to have any
>>JDK 1.4 classes on it, besides tools.jar. Also, I had a script which
>>emulates the Derby build in Gump by building with just one JDK on
>>the classpath for each split, and this script still compiles Derby
>>successfully. Is it possible that a change to Gump (or Ant) was made
>>that is causing JDK 1.4 (or higher) classes to appear on the
>>compilation classpath before the JDK 1.3 classes which are needed
>>for this compile?
>
> IIRC it started to fail after the migration from brutus to vmgump, so
> maybe it really is more of an installation issue.
Hmmm.
> Leo, where did you get the rt.jar that is being used as 1.3 runtime?
Didn't remember, but I just checked, from
http://wiki.apache.org/gump/VmgumpConfig:
TODO: figure out which packages of the below on brutus is needed
lrwxrwxrwx 1 root root 35 Oct 6 2004 ant ->
/opt/__versions__/apache-ant-1.6.2/
lrwxrwxrwx 1 root root 31 Jan 7 11:57 cocoon ->
/opt/__versions__/cocoon-trunk/
lrwxrwxrwx 1 root root 32 Jan 7 11:57 forrest ->
/opt/__versions__/forrest-trunk/
lrwxrwxrwx 1 root root 29 Jan 24 23:47 jdk1.3 ->
/opt/__versions__/jdk1.3.1_14
lrwxrwxrwx 1 root root 27 Oct 6 2004 jdk1.5 ->
/opt/__versions__/jdk1.5.0/
lrwxrwxrwx 1 root root 31 Oct 6 2004 jetty ->
/opt/__versions__/jetty-4.2.21/
lrwxrwxrwx 1 root root 23 Oct 12 2004 kaffe -> /opt/__versions__/kaffe
lrwxrwxrwx 1 root root 29 Oct 6 2004 loader ->
/opt/__versions__/loader-1.0/
lrwxrwxrwx 1 root root 49 Oct 6 2004 mysql ->
/opt/__versions__/mysql-connector-java-3.0.15-ga/
lrwxrwxrwx 1 root root 31 Oct 6 2004 rdflib ->
/opt/__versions__/rdflib-2.0.3/
lrwxrwxrwx 1 root root 30 Oct 6 2004 servlet-api ->
/opt/__versions__/servlet-2.4/
lrwxrwxrwx 1 root root 32 Oct 9 2004 webware ->
/opt/__versions__/Webware-0.8.1/
the "TODO" means I didn't think about it a whole lot and/or gave up.
Further down it says
# update /usr/local/gump/packages/java-runtime-1.3 to have working symlinks
gump@vmgump:/usr/local/gump/packages/java-runtime-1.3$ rm LICENSE
gump@vmgump:/usr/local/gump/packages/java-runtime-1.3$ rm rt.jar
gump@vmgump:/usr/local/gump/packages/java-runtime-1.3$ ln -s
/opt/jdk1.4/LICENSE
gump@vmgump:/usr/local/gump/packages/java-runtime-1.3$ ln -s
/opt/jdk1.4/jre/lib/rt.jar
which obviously means that's the rt.jar from the 1.4 jre that I linked
to, probably because I couldn't figure out some build failure. We don't
have jdk 1.3 on vmgump at the moment I think. Everything on the
classpath is jdk 1.4.
> Is it the one from brutus? Or maybe it is the jikes configuration? I
> vaguely recall we've been running our own version of Jikes on brutus
> while the one on vmgump is a stock debian installed one.
I know I didn't install jikes. Nothing mentioned about it on
http://wiki.apache.org/gump/VmgumpConfig. If we had a custom jikes on
brutus it wasn't in /opt.
What should happen now? Regardless of what you change, please update the
wiki page :-)
You may have noticed I'm working on some sane management of installed
packages for gump3. Will make sure that this kind of thing is a lot
easier to debug than it is now.
cheers!
Leo
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: derby-split-2
Posted by Stefan Bodewig <bo...@apache.org>.
On Tue, 12 Jul 2005, Andrew McIntyre <mc...@gmail.com> wrote:
> Sorry for the delay here...
I've been meaning to look into it myself but never found the time,
sorry.
> However, the classpath reported by Gump doesn't appear to have any
> JDK 1.4 classes on it, besides tools.jar. Also, I had a script which
> emulates the Derby build in Gump by building with just one JDK on
> the classpath for each split, and this script still compiles Derby
> successfully. Is it possible that a change to Gump (or Ant) was made
> that is causing JDK 1.4 (or higher) classes to appear on the
> compilation classpath before the JDK 1.3 classes which are needed
> for this compile?
IIRC it started to fail after the migration from brutus to vmgump, so
maybe it really is more of an installation issue.
Leo, where did you get the rt.jar that is being used as 1.3 runtime?
Is it the one from brutus? Or maybe it is the jikes configuration? I
vaguely recall we've been running our own version of Jikes on brutus
while the one on vmgump is a stock debian installed one.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org