>>> Compiling source in /var/tmp/portage/dev-java/lzma-9.18/work/Java ... * Compiling ... Error: could not open `/opt/icedtea-bin-3.4.0-x86/jre/lib/i386/jvm.cfg' * ERROR: dev-java/lzma-9.18::gentoo failed (compile phase): * ejavac failed * ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 13.0-desktop-gnome_abi32+64_20170706-200324 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.3.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby21 (with Rubygems) * [2] ruby22 (with Rubygems) java-config: The following VMs are available for generation-2: 1) IcedTea JDK 3.4.0 [icedtea-bin-8] *) IcedTea JDK 3.4.0 (x86) [icedtea-bin-8-x86] Available Java Virtual Machines: [1] icedtea-bin-8 [2] icedtea-bin-8-x86 system-vm
Created attachment 482538 [details] emerge-info.txt
Created attachment 482540 [details] dev-java:lzma-9.18:20170709-030353.log
Created attachment 482542 [details] emerge-history.txt
Created attachment 482544 [details] environment
Created attachment 482546 [details] etc.portage.tbz2
Created attachment 482548 [details] temp.tbz2
I'm not sure what happened here as that file is accessible on my system but you're not supposed to use a multilib JVM (icedtea-bin-8-x86) as your system JVM. I don't know whether the tinderbox randomly flips various USE flags but icedtea-bin[multilib] should only be used in the very rare cases where it's needed.
*** Bug 624344 has been marked as a duplicate of this bug. ***
*** Bug 624348 has been marked as a duplicate of this bug. ***
Hhm, multilib is set in make.conf (see attached etc.portage.tbz2) annd ABI="32 64" is activated. Both values are set during setup of a tinderbox image and then never ever changed. The profile is : mr-fox / # ls -ld /etc/portage/make.profile lrwxrwxrwx 1 root root 65 Jul 6 20:04 /etc/portage/make.profile -> ../../usr/portage/profiles/default/linux/amd64/13.0/desktop/gnome All thoses values are choosen randomly at setup but fixed for the lifetime of an image. So is there a combination which should be avoided ?
nevertheless pushed this out : https://github.com/toralf/tinderbox/commit/192edd53c2548d87a223a4398aa82031e85233aa
(In reply to Toralf Förster from comment #10) > Hhm, multilib is set in make.conf (see attached etc.portage.tbz2) annd > ABI="32 64" is activated. Both values are set during setup of a tinderbox > image and then never ever changed. I think some users do it anyway but I believe that multilib is not a flag you should enable manually in your make.conf as it is enabled in the appropriate profiles and masked in others. There is a package.use entry for amd64 that disables multilib for icedtea-bin but make.conf takes precedence over this. I have already been moaned at for not just using the ABI flags on their own but many people (including myself) enable those flags globally so I needed an additional switch. Enabling icedtea-bin[multilib] isn't strictly a problem, just make sure you don't select it as your system JVM.
understood, so setup changed accordingly to that flag : https://github.com/toralf/tinderbox/commit/4919c651da73e7a2f7a1ba11813af87fa5d20ef5
