With Emacs from bzr trunk as of today, I observe the following compile
failure in src/xmenu.c. Complete build log is attached.

   x86_64-pc-linux-gnu-gcc -c  -Demacs -DHAVE_CONFIG_H  -I. -I/var/tmp/portage/app-editors/emacs-vcs-24.0.9999/work/emacs-vcs-24.0.9999/src   -I/usr/include/freetype2    -I/usr/include/alsa   -pthread -D_REENTRANT -DQT_SHARED -I/usr/include/librsvg-2 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng14 -I/usr/include/qt4 -I/usr/include/qt4/QtGui -I/usr/include/libdrm -I/usr/include/qt4/QtCore   -fopenmp -I/usr/include/ImageMagick    -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include        -MMD -MF deps/xmenu.d   -Wimplicit-function-declaration -Wold-style-definition -Wdeclaration-after-statement -Wno-pointer-sign  -march=core2 -ggdb -O2 -pipe xme
 nu.c
   In file included from xmenu.c:104:
   menu.h:36: error: expected ')' before '*' token
   menu.h:37: error: expected ')' before '*' token
   menu.h:40: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
   menu.h:41: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token

Emacs was configured as follows:

   ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --program-suffix=-emacs-24 --infodir=/usr/share/info/emacs-24 --with-crt-dir=/usr/lib64 --without-compress-info --with-sound --with-x --without-gconf --without-xml2 --without-toolkit-scroll-bars --with-gif --with-jpeg --with-png --with-rsvg --with-tiff --with-xpm --with-imagemagick --with-xft --without-libotf --without-m17n-flt --with-x-toolkit=motif --without-hesiod --without-kerberos --without-kerberos5 --with-gpm --with-dbus

   Configured for `x86_64-pc-linux-gnu'.

     Where should the build process find the source code?    /var/tmp/portage/app-editors/emacs-vcs-24.0.9999/work/emacs-vcs-24.0.9999
     What operating system and machine description files should Emacs use?
	   `s/gnu-linux.h' and `m/amdx86-64.h'
     What compiler should emacs be built with?               x86_64-pc-linux-gnu-gcc -march=core2 -ggdb -O2 -pipe
     Should Emacs use the GNU version of malloc?             yes
	 (Using Doug Lea's new malloc from the GNU C Library.)
     Should Emacs use a relocating allocator for buffers?    no
     Should Emacs use mmap(2) for buffer allocation?         no
     What window system should Emacs use?                    x11
     What toolkit should Emacs use?                          MOTIF
     Where do we find X Windows header files?                Standard dirs
     Where do we find X Windows libraries?                   Standard dirs
     Does Emacs use -lXaw3d?                                 no
     Does Emacs use -lXpm?                                   yes
     Does Emacs use -ljpeg?                                  yes
     Does Emacs use -ltiff?                                  yes
     Does Emacs use a gif library?                           yes -lgif
     Does Emacs use -lpng?                                   yes
     Does Emacs use -lrsvg-2?                                yes
     Does Emacs use imagemagick?                             yes
     Does Emacs use -lgpm?                                   yes
     Does Emacs use -ldbus?                                  yes
     Does Emacs use -lgconf?                                 no
     Does Emacs use -lselinux?                               no
     Does Emacs use -lgnutls (BROKEN)?                       yes
     Does Emacs use -lxml2?                                  
     Does Emacs use -lfreetype?                              yes
     Does Emacs use -lm17n-flt?                              no
     Does Emacs use -lotf?                                   no
     Does Emacs use -lxft?                                   yes
     Does Emacs use toolkit scroll bars?                     no