* In order to have cups working with avahi zeroconf support, you need * to have net-dns/avahi emerged with "mdnsresponder-compat" in your USE * flag. Please add that flag, re-emerge avahi, and then emerge cups again. * * ERROR: net-print/cups-1.3.7-r1 failed. * Call stack: * ebuild.sh, line 49: Called pkg_setup * cups-1.3.7-r1.ebuild, line 84: Called die * The specific snippet of code: * die "net-dns/avahi is missing the mdnsresponder-compat feature." * The die message: * net-dns/avahi is missing the mdnsresponder-compat feature. * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/net-print/cups-1.3.7-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/net-print/cups-1.3.7-r1/temp/die.env'. * USE="X acl%* avahi%* dbus jpeg ldap nls pam perl%* php png ppds python%* ssl tiff -java% -kerberos% -samba -slp -static% -zeroconf%" LINGUAS="en%* -de% -es% -et% -fr% -he% -it% -ja% -pl% -sv% -zh_TW%" I'll attach emerge --info Reproducible: Always
Created attachment 153635 [details] emerge --info
See the die message: "net-dns/avahi is missing the mdnsresponder-compat feature." You have avahi installed on your system and the avahi USE flag set for cups, but you need to recompile avahi with USE="mdnsresponder-compat" set in order to compile a avahi enabled cups. If you don't want zeroconf support at all you also have to disable the avahi USE flag for cups as well. (More information regarding avahi/zeroconf in cups can be found over at bug #198267.)
