On Mon, Apr 24, 2017 at 04:07:03PM +0000, J. Roeleveld wrote: > >> I've had the odd rebuild failure here & there, don't bother re-emerging > >> it until revdep-rebuild has finished. Any dependencies it needs would > >> have been rebuilt by then and it should complete without problem.
> Usually an emerge -e @world works. But this time the dependency tree has > some issues as I have had several failures. Here too. The revdep-rebuild only knows portage dependencies. But since it's a rebuild of existing packages, I think it doesn't see any reason to alter the order of merges. Thus we have the occasional failure because a linked-with lib has not yet been rebuilt, so you get an undefined reference. > Now just running the revdeprebuild line till it completes without error. > Then will try an emerge -e again. As I just found out: it will rebuild the entire list of packages again, because gcc-5.4.0 supplies the same libstdc++.so.6 as did gcc-4 (only with different ABI). To counteract that, I wrote the list of packages into a file and feed that to emerge in smaller chunks. That way I can keep tabs ob which packages have already been built (using genlop) and then remove those packages from my list file for subsequent emerge runs. -- Gruß | Greetings | Qapla’ Please do not share anything from, with or about me with any social network. Laziness is the habit of resting before you are tired.
signature.asc
Description: Digital signature
