[SOLVED] OpenJDK compile fails on 32-bit current

canadensis · 03-06-2016, 03:18 AM

Hi,

I am running 32bit current (downloaded 29 Feb 2016). Using ponce's Slackbuilds from http://cgit.ponce.cc/slackbuilds/cur...60302.1.tar.gz I downloaded
the several tarballs in the .info file:

Code:

DOWNLOAD="http://icedtea.classpath.org/download/source/icedtea-2.6.2.tar.xz \
  http://icedtea.classpath.org/download/drops/icedtea7/2.6.2/openjdk.tar.bz2 \
  http://icedtea.classpath.org/download/drops/icedtea7/2.6.2/corba.tar.bz2 \
  http://icedtea.classpath.org/download/drops/icedtea7/2.6.2/jaxp.tar.bz2 \
  http://icedtea.classpath.org/download/drops/icedtea7/2.6.2/jaxws.tar.bz2 \
  http://icedtea.classpath.org/download/drops/icedtea7/2.6.2/jdk.tar.bz2 \
  http://icedtea.classpath.org/download/drops/icedtea7/2.6.2/langtools.tar.bz2 \
  http://icedtea.classpath.org/download/drops/icedtea7/2.6.2/hotspot.tar.bz2"

The compile fails with:

Code:

../../../../src/share/classes/org/omg/CORBA/CODESET_INCOMPATIBLE.java
../../../../src/share/classes/org/omg/CORBA/INVALID_ACTIVITY.java
../../../../src/share/classes/org/omg/CORBA/REBIND.java
../../../../src/share/classes/org/omg/CORBA/TIMEOUT.java
../../../../src/share/classes/org/omg/CORBA/TRANSACTION_MODE.java
../../../../src/share/classes/org/omg/CORBA/TRANSACTION_UNAVAILABLE.java
incorrect classpath: ../../../../src/solaris/classes
Annotation processing got disabled, since it requires a 1.6 compliant JVM
----------
1. ERROR in /tmp/SBo/openjdk/icedtea-build/openjdk-boot/corba/src/share/classes/org/omg/CORBA_2_3/portable/Delegate.java (at line 0)
	/*
	^
Internal compiler error: java.lang.NullPointerException at org.eclipse.jdt.internal.compiler.ReadManager.run(ReadManager.java:173)
----------
java.lang.NullPointerException
   at org.eclipse.jdt.internal.compiler.ReadManager.run(ReadManager.java:173)
   at java.lang.Thread.run(libgcj.so.16)

../../../common/Rules.gmk:184: recipe for target '.compile.classlist' failed
gmake[6]: *** [.compile.classlist] Error 255
gmake[6]: Leaving directory '/tmp/SBo/openjdk/icedtea-build/openjdk-boot/corba/make/org/omg/CORBA'
Makefile:42: recipe for target 'build' failed
gmake[5]: *** [build] Error 1
gmake[5]: Leaving directory '/tmp/SBo/openjdk/icedtea-build/openjdk-boot/corba/make/org/omg'
Makefile:41: recipe for target 'build' failed
gmake[4]: *** [build] Error 1
gmake[4]: Leaving directory '/tmp/SBo/openjdk/icedtea-build/openjdk-boot/corba/make/org'
Makefile:166: recipe for target 'build' failed
gmake[3]: *** [build] Error 1
gmake[3]: Leaving directory '/tmp/SBo/openjdk/icedtea-build/openjdk-boot/corba/make'
make/corba-rules.gmk:42: recipe for target 'corba-build' failed
gmake[2]: *** [corba-build] Error 2
gmake[2]: Leaving directory '/tmp/SBo/openjdk/icedtea-build/openjdk-boot'
Makefile:251: recipe for target 'build_product_image' failed
gmake[1]: *** [build_product_image] Error 2
gmake[1]: Leaving directory '/tmp/SBo/openjdk/icedtea-build/openjdk-boot'
Makefile:2679: recipe for target 'stamps/icedtea-boot.stamp' failed
make: *** [stamps/icedtea-boot.stamp] Error 2
root@T420sl:/home/wjc721/slackbuilds/current-20160302.1/development/openjdk# ^C
root@T420sl:/home/wjc721/slackbuilds/current-20160302.1/development/openjdk# 
root@T420sl:/home/wjc721/slackbuilds/current-20160302.1/development/openjdk#

Any help would be appreciated!

Thanks,
Bill

Alien Bob · 03-06-2016, 03:36 AM

Straight from the README of openjdk.SlackBuild:

Code:

If you get an error like

Internal compiler error: java.lang.NullPointerException at org.eclipse.jdt.internal.compiler.ReadManager.run(ReadManager.java:166)

simply run the build again. This happens early so it shouldn't be that of a
problem. At least 1 out of 5 runs so far have always succeded.

ponce · 03-06-2016, 04:23 AM

hi canadensis, just to clarify: the one you seem to be using is just a snapshot from my personal git repository, that in turn, ATM (in this transitioning phase where current is becoming stable), is more or less what's in SBo's git master (maybe a few days old and with just 2 different scripts).

no need to say you should always read the READMEs included with the build scripts, as they provide useful informations (and sometimes mandatory steps that you have to take to correctly build/install the package).

canadensis · 03-06-2016, 03:17 PM

Alien Bob: thanks, the second attempt worked. To you and ponce I apologise, I asked two silly questions (one in another thread) in quick succession and you were both very patient. I will RTFM before firing off my next question!

ponce: thanks. I built a Slack current machine last month using the 14.1 SlackBuilds and had a problem with RStudio, fixed by using the current SlackBuild. Now I am building another machine, I thought that I would go straight to the current SalckBuilds.

Do you recommend that I use https://slackbuilds.org/cgit/slackbuilds/ rather than your personal git repository?

Cheers, Bill

bassmadrigal · 03-07-2016, 07:17 AM

Quote:

Originally Posted by canadensis

Do you recommend that I use https://slackbuilds.org/cgit/slackbuilds/ rather than your personal git repository?

It's probably easier to actually use sbopkg and set it to use SBo's git repo. willysr has a blog post on how to do this. Make sure you look into sqg to help you get queue files set up for the builds with dependencies.

ponce · 03-07-2016, 08:31 AM

Quote:

Originally Posted by canadensis

Do you recommend that I use https://slackbuilds.org/cgit/slackbuilds/ rather than your personal git repository?

as I said above it's more or less the same in these days of transition to the newer version of Slackware, but usually SBo's git master branch tracks the stable release so you might find issues using it with current (I repeat, not in these days).