Bug 27298 - Can not compile latest version of Libreoffice due to the JDK version being to old; M7 backport request for java-11-openjdk
Summary: Can not compile latest version of Libreoffice due to the JDK version being to...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Backports (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Nicolas Lécureuil
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-21 17:47 CEST by Kristoffer Grundström
Modified: 2021-08-26 06:24 CEST (History)
1 user (show)

See Also:
Source RPM: java-11-openjdk-11.0.9.6-0.0.ea.1.mga8.src.rpm
CVE:
Status comment:


Attachments

Description Kristoffer Grundström 2020-09-21 17:47:00 CEST
Description of problem: I know that we're testing Open JDK 11 and above in Cauldron. However, lets say I want to use the latest official version of Libreoffice and regardless if I clone the git repo or use the svn version that we have.... I end up with this error when I run ./autogen.sh:

checking the installed JDK... configure: error: JDK is too old, you need at least 9 (10800 < 10900)
Error running configure at ./autogen.sh line 299.

So, my question to the package maintainer/packager is:

Can we push an update for the JDK to Mageia 7 or is there no time before Mageia 8 is released?

Version-Release number of selected component (if applicable): 1.8.0.262

How reproducible: All the time.

Steps to Reproduce:
1. Make sure all the build dependancies for Libreoffice are installed.
2. cd to anywhere you want to clone Libreoffice Core repo to.
3. Run git clone --recursive -b master https://github.com/LibreOffice/core.git
4. cd core/
5. Run ./autogen.sh
6. Compiler fails to finish with the error described in the Description of problem part.
Comment 1 Aurelien Oudelet 2020-09-21 18:02:48 CEST
Hi, thanks for reporting this bug.

@Kristoffer, do you run Cauldron or M7?

Currently, we have:
java-1.8.0-openjdk-1.8.0.272.b02-0.0.ea.4.mga8
available in Cauldron Core and installed by default with current Beta1 ISO.

BUT we have:
java-11-openjdk-11.0.9.6-0.0.ea.1.mga8 available in Cauldron Core too!

and

java-latest-openjdk-14.0.2.12-2.rolling.3.mga8 in Cauldron updates_testing.

If you run M8 Cauldron, I suggest you to nuke java-1.8.0-openjdk and replace it by java-11.

Meanwhile, do you want a backport to M7?

Version: Cauldron => 7
CC: (none) => ouaurelien

Comment 2 Kristoffer Grundström 2020-09-21 19:07:42 CEST
I'm running Mageia 7.
I wish for a backport of Java 11 at least to Mageia 7.
Comment 3 Lewis Smith 2020-09-21 20:38:10 CEST
Given your specific motive for this request (up-to-date LibreOffice for Mageia 7), one could suggest you try its Appimage or Flatpak.
The generic request remains valid, however; although the approach of Mageia 8 makes it less likely.

Assigning this to neoclust for java-..-openjdk who can quickly decide about it.

Summary: Can not compile latest version of Libreoffice due to the JDK version being to old => Can not compile latest version of Libreoffice due to the JDK version being to old; M7 backport request for java-11-openjdk
Assignee: bugsquad => mageia
Source RPM: openjdk => java-11-openjdk-11.0.9.6-0.0.ea.1.mga8.src.rpm

Comment 4 Aurelien Oudelet 2021-07-06 13:17:54 CEST
Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.
Comment 5 Kristoffer Grundström 2021-08-26 06:24:51 CEST
Since this report was opened Java has been updated to meet the needs to build Libreoffice so I therefor consider this as a RESOLVED FIXED.

Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.