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 561961 - Build failure: compiler can't find compositor headers even when compositor is disabled
Build failure: compiler can't find compositor headers even when compositor is...
Status: RESOLVED DUPLICATE of bug 560990
Product: metacity
Classification: Other
Component: general
2.24.x
Other All
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2008-11-22 21:54 UTC by Daniel Macks
Modified: 2008-11-23 12:18 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Daniel Macks 2008-11-22 21:54:42 UTC
Please describe the problem:
OS X 10.4 (apple's x11 suite) doesn't have xrandr-1.2 nor some other x11 extensions. Fortunately, metacity-2.24.0 has ./configure flags to disable the now-default use of them. However...

Steps to reproduce:
1. Using fink to supply the support libs (GNOME2.24 versions)
2. ./configure --prefix=/sw --libexecdir=/sw/lib/metacity --mandir=/sw/share/man --disable-dependency-tracking --disable-schemas-install --disable-compositor --disable-render
3. make



Actual results:
At the end of ./configure, the report states "Compositing manager: no" and "Render: no". But during compiling:

gcc -DHAVE_CONFIG_H -I. -I.. -I/sw/lib/fontconfig2/include -I/sw/include/startup-notification-1.0 -I/sw/include/glib-2.0 -I/sw/lib/glib-2.0/include -I/sw/include/dbus-1.0 -I/sw/lib/dbus-1.0/include -I/sw/include/orbit-2.0 -I/sw/include/gconf/2 -I/sw/lib/pango-ft219/include/pango-1.0 -I/sw/lib/freetype219/include/freetype2 -I/sw/lib/freetype219/include -I/sw/include/libpng12 -I/sw/include -I/sw/include/pixman-1 -I/sw/include/cairo -I/sw/include/gtk-2.0 -I/sw/include/atk-1.0 -I/sw/lib/gtk-2.0/include -I/usr/X11R6/include -I/usr/X11/include -DORBIT2=1 -I ./include -DMETACITY_LIBEXECDIR=\"/sw/lib/metacity\" -DHOST_ALIAS=\"\" -DMETACITY_LOCALEDIR=\"/sw/share/locale\" -DMETACITY_PKGDATADIR=\"/sw/share/metacity\" -DMETACITY_DATADIR=\"/sw/share\" -DG_LOG_DOMAIN=\"metacity\" -DSN_API_NOT_YET_FROZEN=1  -I/sw/lib/fontconfig2/include -I/sw/include -I/usr/X11R6/include  -Os -Wall -Wchar-subscripts -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wcast-align -Wsign-compare -c -o compositor-xrender.o `test -f 'compositor/compositor-xrender.c' || echo './'`compositor/compositor-xrender.c
compositor/compositor-xrender.c:46:39: error: X11/extensions/Xcomposite.h: No such file or directory
compositor/compositor-xrender.c:47:36: error: X11/extensions/Xdamage.h: No such file or directory
compositor/compositor-xrender.c:48:35: error: X11/extensions/Xfixes.h: No such file or directory

and then a ton of other errors relating to macros and declarations that would come from those .h

Expected results:
Disabling compositor should disable building of compositor. Disabling render should disable use of a component that sounds like it's based on that extension. At a minimum, need header checks for all specific X11 extensions that might not be available on all systems rather than just xrender & xrandr.

Does this happen every time?
Yes.

Other information:
Comment 1 Thomas Thurman 2008-11-23 12:18:40 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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