GNOME Bugzilla – Bug 311014
clock applet build failure
Last modified: 2005-07-20 22:29:04 UTC
if gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I./../../libpanel-applet -I../../libpanel-applet -Wall -Wmissing-prototypes -D_XOPEN_SOURCE=500 -DORBIT2=1 -pthread -I/opt/gnome210/include/gtk-2.0 -I/opt/gnome210/lib/gtk-2.0/include -I/opt/gnome210/include -I/opt/gnome210/include/atk-1.0 -I/opt/gnome210/include/pango-1.0 -I/opt/gnome210/include/freetype2 -I/usr/X11R6/include -I/opt/gnome210/include/glib-2.0 -I/opt/gnome210/lib/glib-2.0/include -I/opt/gnome210/include/libgnomeui-2.0 -I/opt/gnome210/include/libgnome-2.0 -I/opt/gnome210/include/libgnomecanvas-2.0 -I/opt/gnome210/include/libart-2.0 -I/opt/gnome210/include/gconf/2 -I/opt/gnome210/include/libbonoboui-2.0 -I/opt/gnome210/include/gnome-vfs-2.0 -I/opt/gnome210/lib/gnome-vfs-2.0/include -I/opt/gnome210/include/orbit-2.0 -I/opt/gnome210/include/libbonobo-2.0 -I/opt/gnome210/include/bonobo-activation-2.0 -I/opt/gnome210/include/libxml2 -I/opt/gnome210/include/evolution-data-server-1.4 -DDATADIR=\""/opt/gnome210/share"\" -DLIBDIR=\""/opt/gnome210/lib"\" -DSYSCONFDIR=\""/opt/gnome210/etc"\" -DPREFIX=\""/opt/gnome210"\" -DGNOMELOCALEDIR=\""/opt/gnome210/share/locale"\" -g -D_GNU_SOURCE -L/opt/gnome210/lib -I/opt/gnome210/include -MT clock.o -MD -MP -MF ".deps/clock.Tpo" -c -o clock.o clock.c; \ then mv -f ".deps/clock.Tpo" ".deps/clock.Po"; else rm -f ".deps/clock.Tpo"; exit 1; fi clock.c: In function `config_tool_changed': clock.c:1966: warning: implicit declaration of function `clock_check_config_tool' clock.c: At top level: clock.c:2136: error: conflicting types for 'clock_check_config_tool' clock.c:1966: error: previous implicit declaration of 'clock_check_config_tool' was here clock.c: In function `clock_check_config_tool': clock.c:2148: warning: assignment discards qualifiers from pointer target type clock.c: In function `fill_clock_applet': clock.c:2271: warning: suggest parentheses around assignment used as truth valuemake[3]: *** [clock.o] Error 1
*** Bug 311021 has been marked as a duplicate of this bug. ***
Fixed.