Re: [platform-testers] Emacs 26.2 RC1 is out!

[Eli Zaretskii <eliz@gnu.org>]

> Date: Thu, 21 Mar 2019 16:35:50 -0600
> From: "Nelson H. F. Beebe" <beebe@math.utah.edu>
> Cc: beebe@math.utah.edu
> 
> 	  CC       emacsgtkfixed.o
> 	In file included from /usr/lib/glib-2.0/include/glibconfig.h:9:0,
> 			 from /usr/include/glib-2.0/glib/gtypes.h:32,
> 			 from /usr/include/glib-2.0/glib/galloca.h:32,
> 			 from /usr/include/glib-2.0/glib.h:30,
> 			 from /usr/include/gtk-3.0/gdk/gdkconfig.h:13,
> 			 from /usr/include/gtk-3.0/gdk/gdk.h:30,
> 			 from /usr/include/gtk-3.0/gtk/gtk.h:30,
> 			 from xterm.h:49,
> 			 from emacsgtkfixed.c:25:
> 	emacsgtkfixed.c: In function ‘emacs_fixed_get_type’:
> 	/usr/include/glib-2.0/glib/gmacros.h:232:53: error: size of array ‘_GStaticAssertCompileTimeAssertion_3’ is negative

Sounds like a compatibility problem between GTK headers and that port
of GCC.  IOW, it doesn't look like  an Emacs problem, as those headers
are not Emacs headers.

> However, the lcms2.h header file is installed at
> /usr/include/lcms/lcms2.h, rather than at top level in /usr/include.
> 
> The workaround was easy:
> 
> 	gmake CFLAGS="-I${prefix}/include -I/usr/include/lcms"
> 
> A scan of several of my build farm machines showed that most do not
> even have lcms2, but those that do, have it in /usr/include, EXCEPT
> for some members of the Solaris family (Oracle Solaris and Hipster).
> 
> Presumably, the emacs-26.x configure.ac file could be tweaked to check
> in /usr/include/lcms as well as /usr/include.

Our configure doesn't look for the header file at all, so it isn't
just a matter of adding one more directory to search.

I think we should use pkg-config to detect the correct switches.  Does
that system have an lcms2/pc file and pkg-config, and does the
following command show the correct -I switch:

  pkg-config --cflags lcms2

It's too bad we know this only now, because I don't think I'd like to
delay Emacs 26.2 release due to this issue.  (I believe Emacs 26.1
also doesn't compile on that system for the same reason?)  End users
could either use your workaround or configure without lcms2.

Thanks again for your testing.