Matthias Hanft <m...@hanft.de> wrote: > > Meanwhile I have found out that the culprit is "virtual/jdk".
No, the “culprit” is that you do not use the binary package openjdk and you did apparently in the case of icedtea. Icedtea and openjdk both have cups as a USE-flag, but this influences only the runtime dependency. For building, icedtea and openjdk both need cups. If you install the binary package (icedtea-bin or openjdk-bin), there is no building. I guess that virtual/jdk prefers the non-binary package, and apparently portage is not able to resolve the conflict automatically by letting the binary package satisfy the dependency. If you manually install openjdk-bin, the problem is probably resolved. Be aware to install openjdk-bin:11 and not the meanwhile stable openjdk-bin:17 which does not resolve the virtual/jdk:11 dependency.
