Created attachment 306701 [details] build.log I tried to merge openrc 0.9.9 and got an error about not being able to find einfo.h. Steps to reproduce: - emerge -C openrc - emerge =openrc-0.9.9* Expected result: Openrc 0.9.9 installed Actual result: Compilation failure: librc-misc.c:32:19: fatal error: einfo.h: No such file or directory Note that when I first installed openrc 0.9.8.4 and then upgraded it was fine.
Can you emerge openrc-0.9.9.3?
I didn't specifiy it, but I tried 0.9.9.{0..3} and all gave the same result. Manually placing einfo.h in /usr/include also solved the issue for me.
You shouldn't have to manually place einfo.h in /usr/include however; it is part of the OpenRC source, so there shouldn't be an issue with finding it. I'm about to pull your build log.
Can you please post your emerge --info output?
Created attachment 306757 [details] emerge --info openrc output The reason I placed einfo.h in /usr/include is that when I upgraded to udev 181 I couldn't emerge openrc-0.9.8.4 anymore and I just unmerged openrc. Portage did complain about a file collision when merging. My guess would be that for whatever reason the new openrc doesn't want to use einfo.h from its own sources but only the system file. If openrc is not installed there is no system file so it fails.
Using git bisect on the sources: git bisect start openrc-0.9.9 openrc-0.9.8.4 && git bisect run make clean all c3be42006b78809f1087b6a8262caba01f2c7fc1 is the first bad commit commit c3be42006b78809f1087b6a8262caba01f2c7fc1 Author: Christian Ruppert <idl0r@gentoo.org> Date: Sat Dec 31 00:33:49 2011 +0100 Rename proc_getent to rc_proc_getent and make it global :040000 040000 cded9ad85f6a4326a8ad371bbde68b449e2a444a 8ed69194ea03af8c785aa39a5a037c8c8e962ef1 M src bisect run success
This should be fixed in commit 300c032.
*** Bug 411145 has been marked as a duplicate of this bug. ***
Ok, we have about 10? duplicates now. William, *please* leave this bug open *until* a new version of OpenRC has been released with that fix. Thx.
Damn.. wrong bug.
*** Bug 414041 has been marked as a duplicate of this bug. ***
*** Bug 416319 has been marked as a duplicate of this bug. ***