public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Cc: Dale <rdalek1967@gmail.com>
Subject: Re: [gentoo-user] libkdegames-3.5 won't compile
Date: Mon, 1 Feb 2010 21:55:41 +0200	[thread overview]
Message-ID: <201002012155.41355.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <4B6713AF.3090009@gmail.com>

On Monday 01 February 2010 19:47:27 Dale wrote:
> Well I synced and did a emerge -uvDN world.  It said to run emerge
> @preserved-rebuild and I did.  This is package number one and the error
> doesn't make much since to me.

[snip]

> kgame/.libs/libkgame.a(kgamenetwork.o): In function
> `KGameNetwork::tryPublish()':
> kgamenetwork.cpp:(.text+0x56e): undefined reference to
> `DNSSD::PublicService::PublicService(QString const&, QString const&,
> unsigned int, QString const&)'
> kgame/dialogs/.libs/libkgamedialogs.a(kgameconnectdialog.o): In function
> `KGameConnectWidget::setType(QString const&)':
> kgameconnectdialog.cpp:(.text+0xdb0): undefined reference to
> `DNSSD::ServiceBrowser::ServiceBrowser(QString const&,
> DNSSD::DomainBrowser*, bool)'

This means that the code being built is trying to use a function called 
ServiceBrowser() and it's failing because it doesn't exist or is defined to be 
something different to what the code expects.

[snip]

> I searched around on the forums, bgo and google and found suggestions to
> run lafilefixer --justfixit and revdep-rebuild.  They don't help
> either.  I also tried to use the skipfirst option and just come back to
> it but it complains about this missing package.

Those are useful things to do often anyway, but all too often they are 
presented as the MagicBandAid(tm) solution to all build failures, world hunger 
and stuff that eats kittens. I doubt very much is they will help as none of 
those tips affect compiled libs already in place. 
 
> I'm trying to hang onto KDE 3 and also have KDE 4 installed.  I had to
> change some USE flags to get KDE 4 to upgrade.  One of the flags was
> mDNSResponder.  I don't know if that is related or not.

kdelibs-3.5 on Gentoo had some outlandish requirements - zeroconf was one of 
them. I don't rightly recall which zeroconf method it was - zeroconf, 
mDNSResponder, avahi - but stuff broke horribly without it. What does eix say 
about KDE-3.5 packages using any of those flags? I don't have 3.5 around 
anymore to check here

Also, KDE is heavily interlinked with Qt. A Qt upgrade usually implies a 
rebuild of all of KDE being a very good idea. It's not in DEPEND as KDE 
doesn't so much require a specific Qt version, it's that the built KDE now has 
to work with A higher version of Qt than it was build against. Did you 
recently upgrade Qt?

Have you rebuilt kdelibs than tried building kdegames again?

<side-step workaround>
Have you asked the question "Do I really need all of KDE games?"
</side-step workaround>

-- 
alan dot mckinnon at gmail dot com



  reply	other threads:[~2010-02-01 19:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-01 17:47 [gentoo-user] libkdegames-3.5 won't compile Dale
2010-02-01 19:55 ` Alan McKinnon [this message]
2010-02-01 20:43 ` Arttu V.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201002012155.41355.alan.mckinnon@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    --cc=rdalek1967@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox