Gentoo-prefix system, sys-libs/talloc builds fine but fails on install due to an invalid install name. Looks like the normal fix is a call to install_name_tool in the ebuild.
Depends on the build system. What's the exact error from portage about the install_name?
Created attachment 279517 [details] sys-libs/talloc-2.0.5 build log Adding the build.log, the specific error is as follows: * QA Notice: invalid self-reference install_name /Gentoo/var/tmp/portage/sys-libs/talloc-2.0.5/work/talloc-2.0.5/bin/default/libpytalloc-util.inst.dylib in /Gentoo/usr/lib/libpytalloc-util.2.0.5.dylib * QA Notice: install_name references ${S}: /Gentoo/var/tmp/portage/sys-libs/talloc-2.0.5/work/talloc-2.0.5/bin/default/libtalloc.dylib in /Gentoo/usr/lib/libpytalloc-util.2.0.5.dylib * QA Notice: invalid self-reference install_name /Gentoo/var/tmp/portage/sys-libs/talloc-2.0.5/work/talloc-2.0.5/bin/default/libtalloc.inst.dylib in /Gentoo/usr/lib/libtalloc.2.0.5.dylib * QA Notice: install_name references ${S}: /Gentoo/var/tmp/portage/sys-libs/talloc-2.0.5/work/talloc-2.0.5/bin/default/libtalloc.dylib in /Gentoo/usr/lib/python2.7/site-packages/talloc.bundle * ERROR: sys-libs/talloc-2.0.5 failed: * invalid install_name found, your application or library will crash at runtime
This package uses the brilliant waf system, which -- aside from being binary -- of course reimplements all of autotools, but of course better. This just means they have to build up the rich knowledge that autoconf, automake, libtool and friends have built up over many years as well. Because their system is so smart, it ships itself as binary, such that distributions like Gentoo cannot patch the build system, because that would be rather annoying of course. in short: death to waf. may its developers be enlightened some day soon. fixed now, thanks.
