After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 634790 - libnotify-0.6.0 requires only gtk+3
libnotify-0.6.0 requires only gtk+3
Status: RESOLVED OBSOLETE
Product: libnotify
Classification: Platform
Component: general
0.6.x
Other Linux
: Normal normal
: ---
Assigned To: libnotify-maint
libnotify-maint
Depends on:
Blocks:
 
 
Reported: 2010-11-14 01:45 UTC by Sasa Ostrouska
Modified: 2020-11-26 15:30 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch to add --enable-tests (1.65 KB, patch)
2015-11-19 09:58 UTC, Quentin "Sardem FF7" Glidic
none Details | Review
Patch to add --disable-tests (1.66 KB, patch)
2016-06-14 13:27 UTC, Quentin "Sardem FF7" Glidic
committed Details | Review

Description Sasa Ostrouska 2010-11-14 01:45:36 UTC
Trying to compile libnotify-0.6.0 and configure ends with the following error:

checking pkg-config is at least version 0.9.0... yes
checking for PACKAGE... yes
checking for LINKS... yes
checking for GTK3... configure: error: Package requirements (gtk+-3.0) were not met:

No package 'gtk+-3.0' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables GTK3_CFLAGS
and GTK3_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

Error!  Configure exited with status: 1
Failed package libnotify


In the configure.ac file there is written minimal requirement to be gtk+2
REQ_GTK_VERSION=2.18

Looking in the configure script I do not see the tests for gtk2 only GTK3 tests are in there.

Shouldn't there be a possibility to use it with gtk2 also ?
Comment 1 Sasa Ostrouska 2010-11-14 01:48:35 UTC
Shouldn't there be an option like --with-gtk=2.0 or --with-gtk=3.0 ?

So one can choose.
Comment 2 William Jon McCann 2010-11-14 15:50:47 UTC
GTK+ is only used for the tests now.  I think I'd prefer to just have a --disable-tests argument to configure.  I'd accept a patch for that.
Comment 3 Tobias Mueller 2011-05-06 08:57:23 UTC
Setting to NEW as per last comment.
Comment 4 André Klapper 2012-04-04 10:39:34 UTC
Mass-fixing incorrect Default Assignee and QA contact scheme for libnotify so interested people can follow its development. (See 606365#c1 for ref.)
Comment 5 Quentin "Sardem FF7" Glidic 2015-11-19 09:58:21 UTC
Created attachment 315872 [details] [review]
Patch to add --enable-tests
Comment 6 Quentin "Sardem FF7" Glidic 2016-06-14 13:27:33 UTC
Created attachment 329788 [details] [review]
Patch to add --disable-tests

Reversed the logic so that tests are still build by default.
Comment 7 Marc-Antoine Perennou 2016-06-14 14:09:32 UTC
Review of attachment 329788 [details] [review]:

pushed as da7a6a229b81501a15795d8766731b8523770959
Comment 8 André Klapper 2020-11-26 15:30:59 UTC
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all
older bug reports and feature requests in GNOME Bugzilla which have not seen
updates for a while.

If you still use libnotify and if you still see this bug / want this feature in a recent and currently supported version, then please feel free to report it at
https://gitlab.gnome.org/GNOME/libnotify/-/issues/
by following the guidelines at
https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines

Thank you for creating this report and we are sorry it could not be implemented
so far (volunteer workforce and time is limited).