GNOME Bugzilla – Bug 423990
glibmm et al don't recognize new GNU m4
Last modified: 2008-07-23 13:12:08 UTC
There was a change in the GNU m4 --version output in version 1.4.3. scripts/macros.m4 expects "GNU m4 x.y.z" but current GNU m4 returns "GNU M4 x.y.z" -- the difference being the capitalized M in M4. This causes AL_PROG_GNU_M4 to return no with the newer versions. This affects scripts/macros.m4 in _ALL_ of the C++ bindings.
Thanks. I wonder why I'm not having this problem on Ubuntu Feisty (with m4 1.4.8build1): murrayc@murrayc-desktop:~$ m4 --version GNU M4 1.4.8
Anyway, a patch would be welcome.
Created attachment 86674 [details] [review] scripts/macros.m4 GNU m4 patch > Thanks. I wonder why I'm not having this problem on Ubuntu Feisty (with m4 > 1.4.8build1): "not having this problem" means that the result is yes or that the build still works? AFAICS the test only does something on Solaris if not GNU m4. In any case, patch attached.
Committed to glibmm trunk (2.13) and glibmm-2-12 branch, and to gtkmm trunk (2.10), libglademm, gconfmm, gnome-vfsmm, libgnomecanvasmm, libgnomemm, libgnomeuimm, libgdamm, libgnomedbmm. Tell me if you need it on more branches or modules. Thanks. Please don't forget the ChangeLog entry next time. I'll keep asking for it.
gtksourceviewmm trunk.
Done
This patch is breaking the build for me on Solaris in 2.15.5 tarball. The brackets in "[Mm]" are getting dropped when the code gets into 'configure'. My workaround has been to change: grep '^GNU [Mm]4 ' to grep -i '^GNU m4 ' Should I reopen this bug?
Reopening as the bug still exists for me in 2.17.x.
Could you submit an actual patch, please, ideally against svn, with a ChangeLog entry.
Created attachment 115083 [details] [review] Use grep -i to check for GNU m4. Include ChangeLog entry.
Committed to svn trunk. Thanks. I guess we will see if it stops working for anyone.