Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 111096 - gnome-bluetooth-0.6.0 wrong libbtctl dependency
Summary: gnome-bluetooth-0.6.0 wrong libbtctl dependency
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Alastair Tse (RETIRED)
URL:
Whiteboard:
Keywords: InVCS
: 110668 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-11-01 01:49 UTC by Sven Wegener
Modified: 2005-11-11 05:51 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sven Wegener gentoo-dev 2005-11-01 01:49:50 UTC
Using config source xml::/etc/gconf/gconf.xml.defaults for schema installation
Using $(sysconfdir)/gconf/schemas as install directory for schema files
checking for gob2... /usr/bin/gob2
checking for gob-2 >= 2.0.0... ok
checking for pkg-config... /usr/bin/pkg-config
checking for glib-genmarshal... /usr/bin/glib-genmarshal
checking for libglade-2.0 gobject-2.0 libgnomeui-2.0 >= 1.110.0 gconf-2.0
libbtctl >= 0.5.0... Requested 'libbtctl >= 0.5.0' but version of libbtctl is 0.4.1
configure: error: Library requirements (libglade-2.0 gobject-2.0 libgnomeui-2.0
>= 1.110.0 gconf-2.0 libbtctl >= 0.5.0) not met; consider adjusting the
PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard
prefix so pkg-config can find them.

!!! Please attach the config.log to your bug report:
!!! /var/tmp/portage/gnome-bluetooth-0.6.0/work/gnome-bluetooth-0.6.0/config.log

!!! ERROR: net-wireless/gnome-bluetooth-0.6.0 failed.
!!! Function econf, Line 504, Exitcode 0
!!! econf failed
!!! If you need support, post the topmost build error, NOT this status message.
Comment 1 Henrik Brix Andersen 2005-11-01 06:03:02 UTC
Thanks, fixed in CVS.
Comment 2 Henrik Brix Andersen 2005-11-11 05:51:28 UTC
*** Bug 110668 has been marked as a duplicate of this bug. ***