#1: VirtualBox-4.0.12 fails to build with sys-libs/icu-4.8 because it requires libicuuc.so.46. Solved by installing =sys-libs/icu-4.6.1. #2: VirtualBox-4.0.12 fails to build with USE=-pam when sys-libs/pam not installed. Solved by installing sys-libs/pam. Or need to USE="+pam" in ebuild? Reproducible: Always Steps to Reproduce: #1: 1. emerge -1 =dev-libs/icu-4.8 2. emerge =virtualbox-4.0.12 #2: 1. emerge -C sys-libs/pam ; USE=-pam emerge =virtualbox-4.0.12 Actual Results: #1: VirtualBox fails to build with message "libicuuc.so.46.so not found" #2: VirtualBox fails to build with message "pam_appl.h not found" Expected Results: #1: VirtualBox installed #2: VirtualBox installed
I've removed the pam USE flag again. virtualbox definitely compiels with icu-4.8 so the error must be on your side. Did you run "revdep-rebuild" (belongs to the app-portage/gentoolkit package) after upgrading icu from 4.6.x to 4.8.x?
(In reply to comment #1) > virtualbox definitely compiels with icu-4.8 so the error must be on your side. > Did you run "revdep-rebuild" (belongs to the app-portage/gentoolkit package) > after upgrading icu from 4.6.x to 4.8.x? Yes, variant in 3 steps: 1. upgrade dev-libs/icu to 4.8 2. revdep-rebuild 3. upgrade virtualbox works. Thanks! So... emerge -uDNa world doesn't work in this situation and procedure must be devided in 3 steps: upgrade *-libs/*(what can be more here?), revdep-rebuild, upgrade other packages. It is seems I'll have to rewrite shell-scripts to upgrade my hosts. Thanks again for Your experience! (I'm not shure which status must be ussigned, RESOLVED: INVALID?)
(In reply to comment #2) > (In reply to comment #1) > > virtualbox definitely compiels with icu-4.8 so the error must be on your side. > > Did you run "revdep-rebuild" (belongs to the app-portage/gentoolkit package) > > after upgrading icu from 4.6.x to 4.8.x? > > Yes, variant in 3 steps: > 1. upgrade dev-libs/icu to 4.8 > 2. revdep-rebuild > 3. upgrade virtualbox > works. Thanks! > > So... emerge -uDNa world doesn't work in this situation and procedure must be > devided in 3 steps: upgrade *-libs/*(what can be more here?), revdep-rebuild, > upgrade other packages. > It is seems I'll have to rewrite shell-scripts to upgrade my hosts. From my personal experience I'd say run revdep-rebuild after each update. This reduces the amount of problems related to lib-updates quite a bit. > Thanks again for Your experience! > > (I'm not shure which status must be ussigned, RESOLVED: INVALID?) Let's go with FIXED as the report about pam USE flag was a valid one. Thanks for reporting that.