Summary: | dev-java/sbt-0.13.18 - failed (compile phase) with GENTOO_VM=openjdk-bin-17 - Unrecognized VM option 'CMSClassUnloadingEnabled' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | gentoo, gentoo_bugzilla |
Priority: | Normal | Keywords: | PullRequest |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://github.com/gentoo/gentoo/pull/36491 https://bugs.gentoo.org/show_bug.cgi?id=854717 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge-info.txt
dev-java:sbt-0.13.18:20220531-165615.log emerge-history.txt.bz2 environment etc.portage.tar.bz2 logs.tar.bz2 temp.tar.bz2 build.log from scala-2.12.10-r1 |
Description
Toralf Förster
2022-05-31 17:13:45 UTC
Created attachment 781709 [details]
emerge-info.txt
Created attachment 781712 [details]
dev-java:sbt-0.13.18:20220531-165615.log
Created attachment 781715 [details]
emerge-history.txt.bz2
Created attachment 781718 [details]
environment
Created attachment 781721 [details]
etc.portage.tar.bz2
Created attachment 781724 [details]
logs.tar.bz2
Created attachment 781727 [details]
temp.tar.bz2
Also, scala 2.12.10
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/dev-lang/scala-2.12.10-r1/work/scala-2.12.10 ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/dev-lang/scala-2.12.10-r1/work/scala-2.12.10 ...
* === scala compile ...
Unrecognized VM option 'CMSClassUnloadingEnabled'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
* ERROR: dev-lang/scala-2.12.10-r1::gentoo failed (compile phase):
* sbt compile failed
*
* Call stack:
* ebuild.sh, line 136: Called src_compile
* environment, line 2399: Called die
* The specific snippet of code:
* "${S}"/sbt -Dsbt.log.noformat=true compile || die "sbt compile failed";
*
* If you need support, post the output of `emerge --info '=dev-lang/scala-2.12.10-r1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=dev-lang/scala-2.12.10-r1::gentoo'`.
!!! When you file a bug report, please include the following information:
GENTOO_VM=openjdk-bin-17 CLASSPATH="" JAVA_HOME="/opt/openjdk-bin-17.0.10_p7"
JAVACFLAGS="-source 1.8 -target 1.8" COMPILER=""
and of course, the output of emerge --info =scala-2.12.10
Created attachment 892348 [details]
build.log from scala-2.12.10-r1
(In reply to Joseph from comment #8) > Also, scala 2.12.10 > [...] How did you get there without sbt? Or did I misread "also"? I don't know. It's possible that upgrading sbt failed and it didn't get re-run? Either way, it's clearly failing due to sbt. As of right now, sbt isn't in the list. emerge -uDNpv @world These are the packages that would be merged, in order: Calculating dependencies... done! Dependency resolution took 37.74 s (backtrack: 0/20). [ebuild UD ] dev-lang/scala-2.12.4:2.12/2.12.4::gentoo [2.12.10:2.12/2.12.10::gentoo] USE="emacs -binary -doc -source" 0 KiB Total: 1 package (1 downgrade), Size of downloads: 0 KiB emerge -pv sbt These are the packages that would be merged, in order: Calculating dependencies... done! Dependency resolution took 3.18 s (backtrack: 0/20). [ebuild R ] dev-java/sbt-0.13.18-r1::gentoo USE="-binary" 131.410 KiB Total: 1 package (1 reinstall), Size of downloads: 131.410 KiB according to emerge.log, I last updated sbt on June 9 of 2022: 1654780164: ::: completed emerge (10 of 22) virtual/jdk-1.8.0-r6 to / 1654780164: >>> emerge (11 of 22) dev-java/sbt-0.13.18-r1 to / 1654780164: === (11 of 22) Cleaning (dev-java/sbt-0.13.18-r1::/usr/portage/dev-java/sbt/sbt-0. 13.18-r1.ebuild) 1654780165: === (11 of 22) Compiling/Merging (dev-java/sbt-0.13.18-r1::/usr/portage/dev-java/s bt/sbt-0.13.18-r1.ebuild) 1654780333: === (11 of 22) Merging (dev-java/sbt-0.13.18-r1::/usr/portage/dev-java/sbt/sbt-0.1 3.18-r1.ebuild) 1654780335: >>> AUTOCLEAN: dev-java/sbt:0 1654780335: === Unmerging... (dev-java/sbt-0.13.18) 1654780337: >>> unmerge success: dev-java/sbt-0.13.18 1654780339: === (11 of 22) Post-Build Cleaning (dev-java/sbt-0.13.18-r1::/usr/portage/dev-java /sbt/sbt-0.13.18-r1.ebuild) 1654780339: ::: completed emerge (11 of 22) dev-java/sbt-0.13.18-r1 to / According to the commits, it looks like the day after sbt-0.13.18-r1 was added: https://packages.gentoo.org/packages/dev-java/sbt/changelog So I'd say that I emerged it long ago, and only now is it failing. (In reply to Joseph from comment #13) > according to emerge.log, I last updated sbt on June 9 of 2022: > > 1654780164: ::: completed emerge (10 of 22) virtual/jdk-1.8.0-r6 to / > 1654780164: >>> emerge (11 of 22) dev-java/sbt-0.13.18-r1 to / > 1654780164: === (11 of 22) Cleaning > (dev-java/sbt-0.13.18-r1::/usr/portage/dev-java/sbt/sbt-0. > 13.18-r1.ebuild) > 1654780165: === (11 of 22) Compiling/Merging > (dev-java/sbt-0.13.18-r1::/usr/portage/dev-java/s > bt/sbt-0.13.18-r1.ebuild) > 1654780333: === (11 of 22) Merging > (dev-java/sbt-0.13.18-r1::/usr/portage/dev-java/sbt/sbt-0.1 > 3.18-r1.ebuild) > 1654780335: >>> AUTOCLEAN: dev-java/sbt:0 With those lines you confirm that dev-java/sbt-0.13.18-r1 works for you. The old version 'dev-java/sbt-0.13.18' is long time gone, so this bug #848819 should be closed. For scala, there was bug #854717, "fixed" with https://github.com/gentoo/gentoo/pull/36474/commits/4b7b77c98d. It should also have rbumped the dependency >=dev-java/sbt-${SBTV}:0 in order to trigger the update for cases where old sbt was already installed. |