The tor configure script checks for systemd libraries and fails if systemd is not installed but explicitly enabled. As the ebuild passes $(use_enable systemd), it also has to depend on systemd if the useflag is enabled.
confirmed here : configure: Okay, checking for systemd a different way... checking for SYSTEMD... no configure: error: Explicitly requested systemd support, but systemd not found !!! Please attach the following file when seeking support: !!! /var/tmp/portage/net-misc/tor-0.2.6.10/work/tor-0.2.6.10/config.log * ERROR: net-misc/tor-0.2.6.10::gentoo failed (configure phase): * econf failed * * Call stack: * ebuild.sh, line 93: Called src_configure * environment, line 2901: Called econf '--enable-system-torrc' '--enable-asciidoc' '--docdir=/usr/share/doc/tor-0.2.6.10' '--disable-instrument-downloads' '--disable-bufferevents' '--disable-nat-pmp' '--disable-libscrypt' '--disable-seccomp' '--enable-systemd' '--disable-gcc-hardening' '--disable-linker-hardening' '--disable-transparent' '--disable-upnp' '--disable-tor2web-mode' '--disable-unittests' '--disable-coverage' * phase-helpers.sh, line 662: Called __helpers_die 'econf failed' * isolated-functions.sh, line 117: Called die * The specific snippet of code: * die "$@" * * If you need support, post the output of `emerge --info '=net-misc/tor-0.2.6.10::gentoo'`, * the complete build log and the output of `emerge -pqv '=net-misc/tor-0.2.6.10::gentoo'`. * The complete build log is located at '/var/log/portage/net-misc:tor-0.2.6.10:20150726-132559.log'. * For convenience, a symlink to the build log is located at '/var/tmp/portage/net-misc/tor-0.2.6.10/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/net-misc/tor-0.2.6.10/temp/environment'. * Working directory: '/var/tmp/portage/net-misc/tor-0.2.6.10/work/tor-0.2.6.10' * S: '/var/tmp/portage/net-misc/tor-0.2.6.10/work/tor-0.2.6.10' ----------------------------------------------------------------- This is an stable amd64 chroot image (named amd64-kde-stable_20150724-145811) at a hardened host acting as a tinderbox.
(In reply to Timo Rothenpieler from comment #0) > The tor configure script checks for systemd libraries and fails if systemd > is not installed but explicitly enabled. > > As the ebuild passes $(use_enable systemd), it also has to depend on systemd > if the useflag is enabled. Yeah, obviously. Can you test this patch and I'll commit: Index: tor-0.2.6.10.ebuild =================================================================== RCS file: /var/cvsroot/gentoo-x86/net-misc/tor/tor-0.2.6.10.ebuild,v retrieving revision 1.4 diff -u -B -r1.4 tor-0.2.6.10.ebuild --- tor-0.2.6.10.ebuild 25 Jul 2015 12:30:28 -0000 1.4 +++ tor-0.2.6.10.ebuild 26 Jul 2015 14:36:33 -0000 @@ -26,6 +26,7 @@ nat-pmp? ( net-libs/libnatpmp ) scrypt? ( app-crypt/libscrypt ) seccomp? ( sys-libs/libseccomp ) + systemd? ( sys-apps/systemd ) upnp? ( net-libs/miniupnpc )" RDEPEND="${DEPEND} selinux? ( sec-policy/selinux-tor )"
That patch works fine. tested in chroot tinderbox image amd64-13.0-stable_20150726-185259
