* ERROR: app-admin/syslog-ng-2.1.4 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2328: Called _eapi2_src_compile * ebuild.sh, line 634: Called die * The specific snippet of code: * emake || die "emake failed" * The die message: * emake failed Reproducible: Always Steps to Reproduce: 1. emerge -v syslog-ng Actual Results: * ERROR: app-admin/syslog-ng-2.1.4 failed. Expected Results: Installed syslog-ng
Created attachment 207081 [details] emerge --info This is "emerge --info"
Created attachment 207082 [details] build.log This is "build.log"
Your system seems to be a bit broken, see errors such as /usr/lib64/portage/bin/ebuild.sh: line 449: find: command not found /usr/lib64/portage/bin/ebuild.sh: line 450: xargs: command not found Do you know what happened to your sys-apps/findutils package that should provide 'find' and 'xargs' commands?
(In reply to comment #3) > Your system seems to be a bit broken, see errors such as > > /usr/lib64/portage/bin/ebuild.sh: line 449: find: command not found > /usr/lib64/portage/bin/ebuild.sh: line 450: xargs: command not found > > Do you know what happened to your sys-apps/findutils package that should > provide 'find' and 'xargs' commands? Yes, I know. There was broken USE flags ('cas I used wrong profile) Now I re-emerged "findutils" and unmerged syslog-ng (installed metalog) But if I "emerge -v syslog-ng" there is the same error Attaching new "emerge --info" and "build.log"
Created attachment 207638 [details] emerge --info This is new "emerge --info" (but as I think there is no differences)
Created attachment 207639 [details] build.log This is "build.log" (as I think here would be some diffs)
Same error in a same place...
I think you need to rebuild some more things to recover from the wrong profile :( In this case, dev-libs/glib seems suspicious, because it ought to contain those missing symbols.
Probably user error, closing as invalid. Reopen if not.
After re-emerging world Updating gcc And recompiling kernel Problem now is other place But I would not reopen bug, 'cas...