From: Rostislav Svoboda <rostislav.svoboda@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 54852@debbugs.gnu.org
Subject: [bug#54852] [PATCH] gnu: Add openjdk18.
Date: Tue, 12 Apr 2022 15:03:06 +0200 [thread overview]
Message-ID: <CAEtmmezw36LEg-K+098qJNPXooxi40F+TaqcP7VV45AB8z_jxg@mail.gmail.com> (raw)
In-Reply-To: <e781bf550c921f40077881903271a6e09d01837f.camel@telenet.be>
> Rostislav Svoboda schreef op ma 11-04-2022 om 14:53 [+0200]:
> > + (native-inputs
> > + `(("autoconf" ,autoconf)
> > + ("openjdk17:jdk" ,openjdk17 "jdk")
>
> Does it need openjdk17 to build, or would openjdk16 suffice?
> That would avoid increasing the bootstrap chain length.
Having
("openjdk16:jdk" ,openjdk16 "jdk")
leads to:
configure: Found potential Boot JDK using java(c) in PATH
configure: Potential Boot JDK found at
/gnu/store/j9lyv24nkwgznddiqfv29j2czfn15a9b-openjdk-16.0.1-jdk is
incorrect JDK version (openjdk version "16.0.1" 2021-04-20 OpenJDK
Runtime Environment (build 16.0.1+0-adhoc..source) OpenJDK 64-Bit
Server VM (build 16.0.1+0-adhoc..source, mixed mode, sharing));
ignoring
configure: (Your Boot JDK version must be one of: 17 18)
configure: Could not find a valid Boot JDK. OpenJDK distributions are
available at http://jdk.java.net/.
configure: This might be fixed by explicitly setting --with-boot-jdk
configure: error: Cannot continue
Cheers
Bost
next prev parent reply other threads:[~2022-04-12 13:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 12:53 [bug#54852] [PATCH] gnu: Add openjdk18 Rostislav Svoboda
2022-04-11 13:43 ` Maxime Devos
2022-04-12 13:03 ` Rostislav Svoboda [this message]
2022-04-11 13:44 ` Maxime Devos
2022-04-12 13:24 ` Rostislav Svoboda
2022-04-21 10:27 ` Rostislav Svoboda
2022-04-21 16:38 ` Maxime Devos
2022-04-22 10:59 ` Rostislav Svoboda
2022-04-23 14:38 ` Maxime Devos
2022-04-23 15:11 ` Rostislav Svoboda
2022-04-23 16:10 ` Maxime Devos
2022-04-11 14:15 ` Julien Lepiller
2022-04-13 7:51 ` Björn Höfling
2022-05-08 16:41 ` Maxime Devos
2022-05-09 19:11 ` Maxime Devos
2022-05-09 22:20 ` Rostislav Svoboda
2022-05-10 6:59 ` Maxime Devos
2022-05-11 15:37 ` Rostislav Svoboda
2022-05-11 18:13 ` Maxime Devos
2022-05-11 18:22 ` Maxime Devos
2022-05-11 18:30 ` Maxime Devos
2022-09-27 14:17 ` bug#54852: " Maxim Cournoyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEtmmezw36LEg-K+098qJNPXooxi40F+TaqcP7VV45AB8z_jxg@mail.gmail.com \
--to=rostislav.svoboda@gmail.com \
--cc=54852@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).