* ERROR: media-tv/tvheadend-4.2.4::gentoo failed (configure phase): * econf failed * ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-systemd_20171129-195001 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.2.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python3.6 (fallback) [3] python3.5 (fallback) [4] python2.7 (fallback) Available Ruby profiles: [1] ruby22 (with Rubygems) * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.6.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv media-tv/tvheadend [ebuild N ] media-tv/tvheadend-4.2.4 USE="capmt constcw cwc dvb ffmpeg imagecache inotify systemd timeshift zlib -dbus -debug -dvbcsa -dvben50221 -hdhomerun -iptv -satip -uriparser -xmltv -zeroconf"
Created attachment 508316 [details] emerge-info.txt
Created attachment 508318 [details] emerge-history.txt
Created attachment 508320 [details] environment
Created attachment 508322 [details] etc.portage.tbz2
Created attachment 508324 [details] media-tv:tvheadend-4.2.4:20171205-030051.log
Created attachment 508326 [details] temp.tbz2
Created attachment 509208 [details, diff] Patch I had the same problem and I solved it with the attached patch. I seem to work correctly now, although I also altered the tvheadend.service file. I will attach it for reference use, but it looks less secure then the supplied file.
Created attachment 509210 [details] Alternative tvheadend.service I ended up using this tvheadend.service. The default restrictions made the configuration unaccable and the default muxes unloadable.
(In reply to Mart Kelder from comment #7) > Created attachment 509208 [details, diff] [details, diff] > Patch > > I had the same problem and I solved it with the attached patch. > patch added to system as /etc/portage/patches/media-tv/tvheadend/configure.patch and compiles. Thanks!
This is fixed in 4.2.6, which I have just added. I also adjusted the systemd unit as requested. See bug #654346.