https://bugzilla.novell.com/show_bug.cgi?id=696785 https://bugzilla.novell.com/show_bug.cgi?id=696785#c1 Marcus Meissner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner@novell.com Component|Basesystem |GNOME AssignedTo|bnc-team-screening@forge.pr |bnc-team-gnome@forge.provo. |ovo.novell.com |novell.com Summary|pkg-config fails for glibc |pkg-config fails for glib |(obsolete hook to |(obsolete hook to |glibc-config) |glib-config) --- Comment #1 from Marcus Meissner 2011-05-28 10:05:08 UTC --- glibc != glib. assign to GNOME -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=696785 https://bugzilla.novell.com/show_bug.cgi?id=696785#c3 Dominique Leuenberger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #3 from Dominique Leuenberger 2011-05-28 13:10:58 UTC --- After checking the code I'm not even sure we should remove those handlers (there are a bunch of them). The date back to before pkg-config was widely used and a bunch of were just translated to respective -config scripts. If somebody would have those old libs installed and try to query them using pkg-config the respective -config scripts would be there and return proper values. As such I do not consider this a bug after checking into it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=696785 https://bugzilla.novell.com/show_bug.cgi?id=696785#c5 Dominique Leuenberger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |INVALID --- Comment #5 from Dominique Leuenberger 2011-05-29 16:50:45 UTC --- This would be wrong: Querying for glib does not reflect replying in glib-2.0 answers. Just as much as pkg-config --libs gtk+-2.0 must not answer with any installed gtk+-3.0 info, if gtk2 is not there. A package querying for glib relies on pkg-config replying with glib; glib2 is a API incompatible replacement. If the package queries for glib and the devel parts are not there, a file-not-found error sounds absolutely reasonable. Having to state glib-2.0 for pkg-config is exactly correct. It is NOT the version number of glib itself: it is the stable API version of the library. Currently, glib-2.0.pc actually is of glib2 2.28.6 on my system:

pkg-config --modversion glib-2.0 2.28.6

-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.