Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 222879

Summary: pidgin 2.4.2 does not build if bonjour is not set in USE.
Product: Gentoo Linux Reporter: Michael Pyne <mpyne>
Component: New packagesAssignee: Gentoo Linux bug wranglers <bug-wranglers>
Status: RESOLVED INVALID    
Severity: normal    
Priority: High    
Version: unspecified   
Hardware: AMD64   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: build output for failed build (including configure output)

Description Michael Pyne 2008-05-20 00:12:03 UTC
The pidgin 2.4.2 ebuild includes support for enabling or disabling bonjour support (using avahi), using the USE flag "bonjour".

If this USE flag is disabled then the appropriate configure entry (--disable-avahi) is not passed to the pidgin configure script, causing the build to error out if the avahi dev files are not installed.  This presumably also means that bonjour support is compiled in if support for it is found even if you have disabled it in USE.

I will attach the build.log (there is no config.log).  Portage is version 2.1.5

midna ~ # emerge -pv pidgin

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild     U ] net-im/pidgin-2.4.2 [2.4.1] USE="dbus gstreamer gtk ncurses nls perl spell -bonjour -debug -doc -eds -gadu -gnutls -groupwise -meanwhile -networkmanager -prediction -qq -sasl -silc -tcl -tk -zephyr" 0 kB

Total: 1 package (1 upgrade), Size of downloads: 0 kB
midna ~ # emerge --version
Portage 2.1.5 (default-linux/amd64/2007.0/desktop, gcc-4.2.3, glibc-2.6.1-r0, 2.6.25.3 x86_64)
Comment 1 Michael Pyne 2008-05-20 00:13:24 UTC
Created attachment 153703 [details]
build output for failed build (including configure output)

No config.log was present but I think the build.log file is what you want, this shows the configure output where pidgin complains about avahi being non-existent.
Comment 2 Michael Pyne 2008-05-20 00:19:11 UTC
I thought I had already tried updating but after looking at the ebuild (and actually re-emerging) this bug is already fixed in the Portage tree.  Sorry about the noise.