During world update, could not progress beyond this stage when tried to emerge this version of systemd. Bug filed at request of developer on Gentoo forum
Created attachment 363362 [details] Output of emerge --info and the build log in tar.gz format
(In reply to linux_matt from comment #1) > Created attachment 363362 [details] > Output of emerge --info and the build log Do we have to guess whatkind of binary format it is? gz? bz2? xz? tar.gz? tar.bz2? tar.xz? zip? rar?
These also fail with same error so could be a problem with this specific world update? sys-apps/systemd-208-r2 sys-apps/systemd-208-r1 sys-apps/systemd-207-r2
Could you try with MAKEOPTS=-j1?
(In reply to Michał Górny from comment #4) > Could you try with MAKEOPTS=-j1? Yes, that works,thank you, so it is definitely a configuration issue rather than a bug
No, it's a valid bug. I've just told you a work-around that's an easy way of finding if it's that.
Could you please try to reproduce it with -9999? Something like: MAKEOPTS=-j4 ACCEPT_KEYWORDS='**' emerge -1vB =systemd-9999 This will only build a binary package, so it won't install the live systemd to your system.
Pacho pointed me to a similar bug in libcanberra [1] which points out to libtool ml thread [2] suggesting this may be an automake issue with libraries that are in different install targets. I've added a '-j1' to the ebuild for now. [1]:https://bugs.freedesktop.org/show_bug.cgi?id=28108 [2]:http://lists.gnu.org/archive/html/libtool/2011-03/msg00003.html
*** Bug 487194 has been marked as a duplicate of this bug. ***
On many gnome package running ELTCONF=--reverse-deps elibtoolize solves many relinking issues, not sure if it could also help here :|
I haven't seen this problem for ages... please try to reproduce with 225 version Thanks
