November ’19 release of OpenJDK 8

icedteaToday, icedtea-3.14.0 was released. IcedTea is a software build framework which allows easy compilation of OpenJDK.

The new IcedTea release will build you the latest Java8:  OpenJDK 8u232_b09. This release syncs the OpenJDK support in IcedTea to the official October 2019 security fixes that Oracle released for Java. The release announcement in the mailing list for distro packagers has details about all the security issues and vulnerabilities that are addressed.

I have built Slackware packages for the new Java 8 Update 232 and uploaded them already. Please upgrade at your earliest convenience. Java is still widespread which makes it a popular target for vulnerability attacks.

Here is where you can download the Slackware packages for openjdk and openjre:

If you want to compile OpenJDK 8 yourself you will need apache-ant as well, but otherwise the openjdk/openjre packages have no external dependencies.

Note about usage:

My Java 7 and Java 8 packages (e.g. openjdk7 and openjdk… or openjre7 and openjre) can not co-exist on your computer because they use the same installation directory. You must install either Java 7 or Java 8.

Remember that I release packages for the JRE (runtime environment) and the JDK (development kit) simultaneously, but you only need to install one of the two. The JRE is sufficient if you only want to run Java programs (including Java web plugins). Only in case where you’d want to develop Java programs and need a Java compiler, you are in need of the JDK package.

Enjoy! Eric

19 thoughts on “November ’19 release of OpenJDK 8


  1. Pingback: Links 16/11/2019: Wine 4.20, Picolibc 1.1 | Techrights


  2. Eric,

    I was building a liveslack iso and noticed that libXau is missing from the x_base.lst in the packages sub-directory of the liveslack git.

    Jim



  3. Thank you Alienbob for the update. Now the jnlp file that failed for me works. I used latest plasma livedvd, and used slackpkg install icedtea-web because javaws was not found when I first ran it.


  4. Alienbob great work…. i recetly installed a Slackware remote desktop server using VNC and multiuser concurrent is very stable, great distro!




    1. sratom, sord, and serd are dependencies of audacity dependencies. I only list the direct dependencies, so you’d have to walk the dependency chain to find them all.



  5. I need advice to build icedtea-web from Slackbuild on slackware-current arm version.
    I have successfully installed slackware-arm on a raspberry pi 4 with the packages available from http://sarpi.fatdog.eu/.
    I am using a jdk package
    http://sarpi.fatdog.eu/files/pkg/jdk-7u45-arm-1_slack14.2_sp1.txz
    When building the icedtea-web package I get the following:
    I get error seamonkey-plugins

    checking JDK version... java version "1.8.0_221"
    Java(TM) SE Runtime Environment (build 1.8.0_221-b11)
    Java HotSpot(TM) Server VM (build 25.221-b11, mixed mode)
    checking for javadoc... /usr/lib/java/bin/javadoc
    checking whether javadoc supports -J options... yes
    checking for keytool... /usr/lib/java/bin/keytool
    checking for jarsigner... /usr/lib/java/bin/jarsigner
    checking for pack200... /usr/lib/java/bin/pack200
    checking for hg... /usr/bin/hg
    checking for IcedTea Mercurial revision ID... none
    checking for distribution package version... Slackware-14.2+-arm
    checking what version string to use... 1.7 (Slackware-14.2+-arm)
    checking whether to build the browser plugin... yes
    checking for pkg-config... /usr/bin/pkg-config
    checking pkg-config is at least version 0.9.0... yes
    checking for GLIB... yes
    checking for MOZILLA... no
    checking for MOZILLA... no
    configure: error: Package requirements (seamonkey-plugin) were not met:

    No package 'seamonkey-plugin' found

    Consider adjusting the PKG_CONFIG_PATH environment variable if you
    installed software in a non-standard prefix.

    Alternatively, you may set the environment variables MOZILLA_CFLAGS
    and MOZILLA_LIBS to avoid the need to call pkg-config.
    See the pkg-config man page for more details.
    make: *** No targets specified and no makefile found. Stop.
    make: *** No targets specified and no makefile found. Stop.

    Since you successfully built icedtea-web and openjdk on slackware I turn to your expertise. I have successfully used your packages before. I appreciate your help and hope not to bother you in your work.



  6. I have installed everything from slackware arm and it is not there. Where can I find a copy? Seamonkey is installed.

    root@pi4-E154-EHS:~# slackpkg search seamonkey-solibs

    Looking for seamonkey-solibs in package list. Please wait... DONE

    No package name matches the pattern.

    root@pi4-E154-EHS:~#

    I find prerelease versions of 1.8.
    http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2019-February/041166.html
    and I tried a portable one but it failed to work. I have java installed but not the javaws executable provided by icedtea-web package.
    They have newer versions
    https://adoptopenjdk.net/icedtea-web.html
    But they fail to build on the pi4 raspberry machine.
    https://github.com/AdoptOpenJDK/IcedTea-Web

    Downloads pi4-E154-EHS [Wed Dec 18] 14:26 $ which javac
    /usr/lib/java/bin/javac
    Downloads pi4-E154-EHS [Wed Dec 18] 14:26 $ which java
    /usr/lib/java/bin/java
    Downloads pi4-E154-EHS [Wed Dec 18] 14:26 $ which javaws
    which: no javaws in (/usr/bin/kertex:/opt/schily/bin:PATH=/usr/local/bin:/usr/bin:/bin:/usr/games:/usr/lib/java/bin:/usr/lib/java/jre/bin:/usr/lib/kde4/libexec:/usr/lib/qt/bin)
    Downloads pi4-E154-EHS [Wed Dec 18] 14:26 $


    1. Looks like Slackware ARM does not split off the shared libraries of Seamonkey in a separate “seamonkey-solibs” package. If you installed seamonkey, you have installed everything that would be in a “-solibs” package.

      If you look at my SlackBuild script for icedtea-solibs you’ll see that I patch the configure script to look for seamonkey instead of xulrunner: https://git.slackware.nl/asb/tree/icedtea-web/build/icedtea-web.SlackBuild#n84
      I assume you are not using my SlackBuild script then.


  7. Dear Sir,

    I am using your SlackBuild. I know you have packages for 586 and x86_64 machines. See below

    Downloads pi4-E154-EHS [Wed Dec 18] 15:08 $ cd icedtea-web
    icedtea-web pi4-E154-EHS [Wed Dec 18] 15:08 $ ls
    doinst.sh.gz icedtea-web-1.7.tar.gz icedtea-web.SlackBuild slack-desc
    icedtea-web pi4-E154-EHS [Wed Dec 18] 15:08 $ su -c ‘./icedtea-web.SlackBuild ‘
    Password:
    Extracting…
    checking for a BSD-compatible install… /bin/ginstall -c
    checking whether build environment is sane… yes
    checking for a thread-safe mkdir -p… /bin/mkdir -p
    checking for gawk… gawk
    checking whether make sets $(MAKE)… yes
    checking whether make supports nested variables… yes
    checking how to create a pax tar archive… gnutar
    checking whether to enable maintainer-specific portions of Makefiles… yes
    checking build system type… arm-slackware-linux-gnueabi
    checking host system type… arm-slackware-linux-gnueabi
    checking for gcc… gcc
    checking whether the C compiler works… yes
    checking for C compiler default output file name… a.out
    checking for suffix of executables…
    checking whether we are cross compiling… no
    checking for suffix of object files… o
    checking whether we are using the GNU C compiler… yes
    checking whether gcc accepts -g… yes
    checking for gcc option to accept ISO C89… none needed
    checking whether gcc understands -c and -o together… yes
    checking for style of include used by make… GNU
    checking dependency style of gcc… none
    checking for g++… g++
    checking whether we are using the GNU C++ compiler… yes
    checking whether g++ accepts -g… yes
    checking dependency style of g++… none
    checking if cp supports –reflink… yes
    checking if we can hard link rather than copy from /tmp/icedtea-web-1.7… yes
    checking whether to build documentation… no
    checking whether to filter by whitelisting on directory name when processing, compiling and running reproducers… no
    checking for bash… /bin/bash
    checking whether to compile ecj natively… no
    checking for zip… /usr/bin/zip
    checking for a JDK home directory… /usr/lib/java (link to /usr/lib/java)
    checking for javac… /usr/lib/java/bin/javac
    checking for ecj… no
    checking for ecj-3.1… no
    checking for ecj-3.2… no
    checking for ecj-3.3… no
    checking if we are using ecj as javac… no
    checking for jar… /usr/lib/java/bin/jar
    checking whether jar supports @ argument… yes
    checking whether jar supports stdin file arguments… no
    checking whether jar supports -J options at the end… yes
    checking for an ecj JAR file… no
    checking for a JRE home directory… /usr/lib/java/jre (link to /usr/lib/java/jre)
    checking for a Java virtual machine… /usr/lib/java/jre/bin/java
    checking JDK version… java version “1.8.0_221”
    Java(TM) SE Runtime Environment (build 1.8.0_221-b11)
    Java HotSpot(TM) Server VM (build 25.221-b11, mixed mode)
    checking for javadoc… /usr/lib/java/bin/javadoc
    checking whether javadoc supports -J options… yes
    checking for keytool… /usr/lib/java/bin/keytool
    checking for jarsigner… /usr/lib/java/bin/jarsigner
    checking for pack200… /usr/lib/java/bin/pack200
    checking for hg… /usr/bin/hg
    checking for IcedTea Mercurial revision ID… none
    checking for distribution package version… Slackware-14.2+-arm
    checking what version string to use… 1.7 (Slackware-14.2+-arm)
    checking whether to build the browser plugin… yes
    checking for pkg-config… /usr/bin/pkg-config
    checking pkg-config is at least version 0.9.0… yes
    checking for GLIB… yes
    checking for MOZILLA… no
    checking for MOZILLA… no
    configure: error: Package requirements (seamonkey-plugin) were not met:

    No package ‘seamonkey-plugin’ found

    Consider adjusting the PKG_CONFIG_PATH environment variable if you
    installed software in a non-standard prefix.

    Alternatively, you may set the environment variables MOZILLA_CFLAGS
    and MOZILLA_LIBS to avoid the need to call pkg-config.
    See the pkg-config man page for more details.
    make: *** No targets specified and no makefile found. Stop.
    make: *** No targets specified and no makefile found. Stop.
    icedtea-web pi4-E154-EHS [Wed Dec 18] 15:08 $

    I look for seamonkey*

    <quicedtea-web pi4-E154-EHS [Wed Dec 18] 15:08 $ ls /var/log/packages | grep 'seamonkey'
    seamonkey-2.49.5-arm-2

    I appreciate your help with this matter.


    1. Well, since I do not have an ARM system running Armedslack, I guess you’ll have to find out yourself. I have given you all the pointers I can give. The rest is up to you.


  8. I have found out what happened. I appreciate your help and apologize for being a pest. I know you work very hard and package many packages for us slackware users. On a changelog

    ftp://ftp.arm.slackware.com/slackwarearm/slackwarearm-current/ChangeLog.txt

    +————————–+
    Mon Sep 09 08:08:08 UTC 2019
    **** removed for purpose of saving space *****
    l/seamonkey-solibs-2.49.5-arm-1.txz: Removed.
    This package was included years ago to support a few things that needed
    nss/nspr, but we’ve since included that in the mozilla-nss package.
    Nothing should be using this anymore.

    xap/seamonkey-2.49.5-arm-1.txz: Upgraded.
    This release contains security fixes and improvements.
    For more information, see:
    http://www.seamonkey-project.org/releases/2.49.5
    Added additional options to more closely match the official build:
    –enable-rust –enable-js-shell –enable-release
    –enable-calendar
    Thanks to ljb643 for the bug report.
    Removed /usr/lib{,64}/seamonkey from /etc/ld.so.conf.
    (* Security fix *)
    +————————–+

    I used a slackBuild for Mozplugger, and commented this but it still does not find it. I will keep working at it. I appreciate your help and apologize again. If I can find out how to work it out, I will post back.


    1. Hi Antonio,
      No need to apologize. It’s a non-trivial issue and I hope I gave you enough pointers.
      Not having Slackware ARM running on any machine limits my ability to do troubleshooting. I can only share my past experiences instead of actually trying to reproduce your issue.


Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.