Summary: | net-dns/avahi-0.6.22-r1 - configure fails to find qt-mt.pc | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kristian Niemi <kristian.niemi> |
Component: | New packages | Assignee: | Sven Wegener <swegener> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | phajdan.jr, txl263 |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | net-dns/avahi-0.6.22-r1/work/avahi-0.6.22/config.log |
Description
Kristian Niemi
2008-05-19 12:19:13 UTC
Please test, if rebuilding Qt 3 fixes the problem for you. Please provide the config.log from the work directory as well. (In reply to comment #1) > Please test, if rebuilding Qt 3 fixes the problem for you. > I did mention that I had tried reinstalling QT and that it did not help -- as did another person on the forum thread mentioned as well, so it's not unique for my setup --, though I might have emphasized it more as it's easily overlooked in such a lengthy post as the initial one was. But, that said, reinstalling does have a magickal way of sorting things out, so I installed QT (3) again, just for the heck of it. It did not help. Ended in exactly the same error. Created attachment 153685 [details]
net-dns/avahi-0.6.22-r1/work/avahi-0.6.22/config.log
(Was too long to include in message.)
As mentioned in the original post (see NOTE), kdnssd-avahi-0.1.2 also fails after avahi has successfully been built (PKG_CONFIG_PATH having been specified in bashrc). Should a separate bug report be filed for kdnssd-avahi-0.1.2? I did not do it originally, as I assumed it might be fixed by getting avahi to compile `the right way'(tm). But on the other hand, it's a separate package, so...? Wait and see, or file and be done with it?-) What's the contents of /etc/env.d/*qt*? There should be one file with PKG_CONFIG_PATH in it, which should end up in /etc/profile.env. You use paludis for building packages? Snippet from /etc/env.d/45qt3: "PKG_CONFIG_PATH=/usr/qt/3/lib/pkgconfig" Snippet form /etc/profile.env: "export PKG_CONFIG_PATH='/usr/qt/3/lib/pkgconfig'" Yes, I use paludis. As I've been perfectly capable to compile other packages that depends on QT with paludis, I didn't think it was the culprit. To be able to say as much, I just tried emerging it with portage -- QT3 _was_ found in the configuration phase. So in short: using emerge solved my problem. Thanks for your time! I'll post a link about this to the paludis thread so they can take a look. I just ran into this problem on a fresh install on a new amd64 system. This is the first time qt was installed, and the first time avahi was installed. I managed to solve it by running the following commands, in the shell I was installing things with paludis: env-update source /etc/profile So, my guess would be that paludis doesn't regenerate the environment after every merge, whereas emerge does. That is just a guess, though. Package qt-mt was not found in the pkg-config search path. Perhaps you should add the directory containing `qt-mt.pc' For example gentoo ~ # locate qt-mt.pc /usr/qt/3/lib/pkgconfig/qt-mt.pc gentoo ~ # export PKG_CONFIG_PATH=/usr/qt/3/lib/pkgconfig/:$PKG_CONFIG_PATH then reemerge avahi with USE="qt3" All be ok! This should be fixed by, 03 Jan 2010; Samuli Suominen <ssuominen@gentoo.org> avahi-0.6.24-r2.ebuild, avahi-0.6.25.ebuild: Remove unused USE="qt3" support wrt bug #283429. |