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 594045 - gnome-panel/applet/clock build fails due to wrong cflags
gnome-panel/applet/clock build fails due to wrong cflags
Status: RESOLVED DUPLICATE of bug 597479
Product: gnome-panel
Classification: Other
Component: clock
git master
Other Linux
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-09-03 14:58 UTC by Joel Bosveld
Modified: 2010-01-14 03:17 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Add gnome-desktop-2.0 requirement for libpanel_applet (696 bytes, patch)
2009-09-03 14:58 UTC, Joel Bosveld 		none Details | Review

Description Joel Bosveld 2009-09-03 14:58:27 UTC 
Created attachment 142412 [details] [review]
Add gnome-desktop-2.0 requirement for libpanel_applet

Latest (as of now-ish) git fails with:

"calendar-window.c:46:42: error: libgnome/gnome-desktop-utils.h: No such file"

The attached patch adds a gnome-desktop-2.0 requirement to libpanel_applet,
which make it put "-I${the_right_path_to_gnome-desktop-2.0}" when compiling and
thus everything works.
Comment 1 ts.salvador 2009-10-23 02:37:07 UTC 
I can confirm I had the exact same problem. And wrote a very similar patch to solve it.
Comment 2 Wang Xin 2009-12-08 05:17:25 UTC 
I had the same problem and fixed it by adding gnome-desktop-2.0 to CLOCK_CFLAGS and CLOCK_LIBS. And I think broken build is a high priority problem
Comment 3 Vincent Untz 2010-01-14 03:17:58 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 597479 ***