GNOME Bugzilla – Bug 162109
[build] removing unused gettext m4 macros
Last modified: 2006-04-11 15:44:04 UTC
On my system, I can't regenerate the aclocal.m4 file of gstreamer. The problem is that I don't have the last four macros that the AM_INTL_SUBDIR macro AC_REQUIREs (in gstreamer/common/m4/gettext.m4) Moreover it looks like those macros are not used. Would it be possible to remove them from gettext.m4 or at least to remove the ones that are AC_REQUIREd ? Thanks for any suggestion about that. Vincent.
Uh, I'm not following. Those files are put there by autogen.sh through the autopoint run. What version of autopoint/gettext do you have installed ? These files are not in CVS so it's not just a matter of removing them :) Can you show me complete output of ./autogen.sh ?
i think was he means is : remove AC_REQUIRES in configure.ac that force autogen to add those gettext specific m4 we're using intltool for i18n, right ? or both intltool and gettext ?
Yes, that's what I meant. Unfortunately I can't show you the output of autogen.sh because we don't use it (I hope I won't be punished for that). In fact we have our own build environment which does the same (that is regenerate aclocal.m4, the Makefile.in files, the configure script...) The phase that is failing is the reconstruction of the aclocal.m4 file because of the reason stated above. The macros that aclocal is not finding are : gt_INTDIV0 jm_AC_TYPE_UINTMAX_T gt_HEADER_INTTYPES_H] gt_INTTYPES_PRI which are AC_REQUIREd by a macro (AM_INTL_SUBDIR) which is not used in the configure.ac file. I use gettext-0.10.40. I hope I won't have to change it unless I really have to. Thanks.
Stephane: - there is no AC_REQUIRE for gettext in configure.ac - we don't use intltool, we use gettext (more specifically, autopoint) Vincent: - I don't see an AM_INTL_SUBDIR in configure.ac - I don't understand why you don't use autogen.sh - at the very least, if you want me to help on this, I'd need to see the script you use to build and the output you get from it. I really don't see what you would suggest I change in our build that solves the problem with your specialized s3kr3t build.
stephane, vincent: ping on this bug
setting as NEEDINFO