User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.3) Gecko/20060326 Firefox/1.5.0.3 (Debian-1.5.dfsg+1.5.0.3-2) Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.3) Gecko/20060326 Firefox/1.5.0.3 (Debian-1.5.dfsg+1.5.0.3-2) checking whether we can use the xf86misc extension... no checking whether we can use the XKB extension... no checking whether we can use the XRANDR extension... no checking whether we can use the Xxf86vm extension... no But, when i force -DUSE_XKB in the Makefile.am build succeeds (and the keyboard-settings plugin works as expected. If all tests fail in the configure script, there is no way the keyboard-settings dialog can work. ./configure --enable-xkb ./configure --enable-xf86misc both do not make the tests succeed. (TRY_LINK seems to fail) Reproducible: Always
config.log? Works fine here.
Created attachment 594 config.log Attached config.log
Hmm, it looks like X_CFLAGS is empty, and therefore LIBX11_CFLAGS isn't getting set, so it can't find the X headers. The compilation of the module itself works OK because /usr/X11R6/include is pulled in by gtk's CFLAGS. Benny, your auto-foo is much stronger than mine... any ideas?
(In reply to comment #3) > Hmm, it looks like X_CFLAGS is empty, and therefore LIBX11_CFLAGS isn't getting > set, so it can't find the X headers. The compilation of the module itself > works OK because /usr/X11R6/include is pulled in by gtk's CFLAGS. Benny, your > auto-foo is much stronger than mine... any ideas? > This was a bug introduced by debian at some point, i updated and now it works. I'll set it to 'worksforme' now.