Re: [gentoo-desktop] KDE-Sunset : kdelibs problem

[E. Liddell]

On Mon, 29 Oct 2012 13:01:19 -0400
Philip Webb <purslow@××××××××.net> wrote:

> 121029 Fat-Zer wrote:
> > 2012/10/29 E. Liddell <ejlddll@××××××××××.com>
> >> Your real problem was that you were trying to emerge kdelibs-3.5.10-*r6*,
> >> rather than 3.5.10-r10, which has a patch for openssl > 1.0.0
> >> and compiled just fine for me as of Thursday.
> > The truth is yours: it compiles.
>
> I did realise that & tried it, but what I then got was :
>
>   root:506 ~> USE="avahi qt3" emerge kdelibs:3.5
>   ...
>   >>> Emerging (1 of 3) net-dns/avahi-0.6.30-r1 from kde-sunset
>   * avahi-0.6.30.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ]
>   >>> Unpacking source...
>   >>> Unpacking avahi-0.6.30.tar.gz to /z/portage-tmp/portage/net-dns/avahi-0.6.30-r1/work
>   >>> Source unpacked in /z/portage-tmp/portage/net-dns/avahi-0.6.30-r1/work
>   >>> Preparing source in /z/portage-tmp/portage/net-dns/avahi-0.6.30-r1/work/avahi-0.6.30 ...
>   * Applying avahi-0.6.30-optional-gtk-utils.patch ... [ ok ]
>   * Running eautoreconf in '/z/portage-tmp/portage/net-dns/avahi-0.6.30-r1/work/avahi-0.6.30' ...
>  * Running glib-gettextize --copy --force ... [ ok ]
>  * Running intltoolize --automake --copy --force ... [ ok ]
>  * Running libtoolize --install --copy --force --automake ... [ ok ]
>  * Running aclocal -I common ... [ ok ]
>  * Running autoconf ... [ ok ]
>  * Running autoheader ... [ ok ]
>  * Running automake --add-missing --copy --foreign ... [ !! ]
>  * Failed Running automake !
>  * Include in your bugreport the contents of:
>  *   /z/portage-tmp/portage/net-dns/avahi-0.6.30-r1/temp/automake.out
>
> which contains :
>
>   ***** automake *****
>   ***** PWD: /z/portage-tmp/portage/net-dns/avahi-0.6.30-r1/work/avahi-0.6.30
>   ***** automake --add-missing --copy --foreign
>   configure.ac:143: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body
>   ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from...
>   ../../lib/autoconf/general.m4:2591: _AC_COMPILE_IFELSE is expanded from...
>   ../../lib/autoconf/general.m4:2607: AC_COMPILE_IFELSE is expanded from...
>   ../../lib/m4sugar/m4sh.m4:606: AS_IF is expanded from...
>   ../../lib/autoconf/general.m4:2032: AC_CACHE_VAL is expanded from...
>   ../../lib/autoconf/general.m4:2053: AC_CACHE_CHECK is expanded from...
>   configure.ac:143: the top level
>   configure.ac:300: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body
>   ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from...
>   configure.ac:300: the top level
>   service-type-database/Makefile.am:21: `pkglibdir' is not a legitimate directory for `DATA'
>
> Do either of you have further suggestions ? -- thanks so far (smile)

If I'm reading that correctly, your compile failure is in avahi itself, not any of
the kde-sunset packages.  avahi is still in the main tree, so complaints about it
should be addressed to the main Gentoo Bugzilla . . . and it looks like
avahi-0.6.30-r3 is the current stable ebuild for nearly all arches, not -r1,
unless it's been rolled back since I last did emerge --sync.

As for what to do with kdelibs, my advice would be to compile it with -avahi and
let it fall back on mDNSResponder instead.  If that is unacceptable to you for
some reason, and you get avahi to compile, you could try hacking the avahi ebuild
to turn QT3 support back on (try replacing the line that says "--disable-qt3 \" with
"--enable-qt3 \")--that probably won't help, mind you, but it's worth a try.

The next step after that would involve checking both the Trinity and the OpenSUSE
KDE3 repos for patches to kdnssd-avahi and seeing if they have something that
fixes the problem (may require patch tweaking).  If there's nothing relevant, writing
a patch from scratch is the only workable approach, and it's probably more trouble
than you want to go to.