Cannot build icedtea-bin on arm without alsa: >>> Emerging (12 of 15) dev-java/icedtea-bin-3.4.0::gentoo * icedtea-bin-core-3.4.0-arm.tar.xz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking icedtea-bin-core-3.4.0-arm.tar.xz to /var/tmp/portage/dev-java/icedtea-bin-3.4.0/work >>> Source unpacked in /var/tmp/portage/dev-java/icedtea-bin-3.4.0/work >>> Preparing source in /var/tmp/portage/dev-java/icedtea-bin-3.4.0/work ... removed ‘icedtea-bin-3.4.0-arm/jre/lib/aarch32/libjsoundalsa.so’ rm: cannot remove ‘icedtea-bin-3.4.0-arm/jre/lib/arm/libjsoundalsa.so’: No such file or directory * ERROR: dev-java/icedtea-bin-3.4.0::gentoo failed (prepare phase): * (no error message) * * Call stack: * ebuild.sh, line 115: Called src_prepare * environment, line 1709: Called die * The specific snippet of code: * rm -v */jre/lib/*/libjsoundalsa.* || die; * * If you need support, post the output of `emerge --info '=dev-java/icedtea-bin-3.4.0::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-java/icedtea-bin-3.4.0::gentoo'`. * The complete build log is located at '/var/tmp/portage/dev-java/icedtea-bin-3.4.0/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-java/icedtea-bin-3.4.0/temp/environment'. * Working directory: '/var/tmp/portage/dev-java/icedtea-bin-3.4.0/work' * S: '/var/tmp/portage/dev-java/icedtea-bin-3.4.0/work' Reproducible: Always
More info: emerging on arm: dev-java/icedtea-bin-3.4.0:8::gentoo USE="headless-awt webstart -alsa -cups -doc -examples -gtk (-multilib) -nsplugin -pulseaudio (-selinux) -source" the following files fail to be removed: icedtea-bin-3.4.0-arm/jre/lib/arm/libjsoundalsa.so icedtea-bin-3.4.0-arm/jre/lib/arm/libawt_xawt.so icedtea-bin-3.4.0-arm/jre/lib/arm/libjawt.so icedtea-bin-3.4.0-arm/jre/lib/arm/libsplashscreen.so
Thank you for the report. Please attach the logfiles https://wiki.gentoo.org/wiki/Bugzilla/Bug_report_guide#Problems_at_build_time
Sorry, I did not save the log files. It is clear what the problem is, and I modified the ebuild to continue on removal failures, and it worked fine. I expect that it will be clear to maintainers what to do as well.
Fixed! This issue was specific to arm and new in this release.
