Build system problems are difficult to handle because there is really no way to make sure a change won't break someone else's build. (And note that this holds independent of the particular build system in use.)
At the autogen level, in practice, what I do is to make sure things work for me, Andreas, and Jean. The method is that they tell me when I break something and we hash it out. It doesn't scale. At the tarball level there is a slow feedback from distributions. The major ones are pretty good at letting me know of problems, generally arising from them using newer dependents than I do. Now, specifically m4/glib-gettext.m4. You probably had a copy from a previous version of your distribution, i.e., from before a system upgrade. That happens, but I can't really tell the difference between an edited file and an old file, so blowing the file away unconditionally seems unwise. Morten On Sun, Oct 29, 2017 at 11:59 AM, Frédéric Parrenin <frederic.parre...@univ-grenoble-alpes.fr> wrote: > Answering to myself. > The solution is to delete the file m4/glib-gettext.m4. > Note that gnumeric is also affected. > Maybe it is worth a fix in the build system? > > Best, > > Frédéric > > > Le 24/10/2017 à 16:21, Frédéric Parrenin a écrit : >> >> Dear all, >> >> Today I tried to compile the git version of goffice. >> I get the following error message when running ./autogen.sh: >> >> root@lgge179:/usr/local/goffice# ./autogen.sh >> m4/glib-gettext.m4:39: error: m4_copy: won't overwrite defined macro: >> glib_DEFUN >> m4/glib-gettext.m4:39: the top level >> autom4te: /usr/bin/m4 failed with exit status: 1 >> aclocal: error: echo failed with exit status: 1 >> >> Any help would be appreciated! >> >> Thanks, >> >> Frédéric >> > > _______________________________________________ > gnumeric-list mailing list > gnumeric-list@gnome.org > https://mail.gnome.org/mailman/listinfo/gnumeric-list _______________________________________________ gnumeric-list mailing list gnumeric-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnumeric-list
