On Mon, Nov 16, 2009 at 12:23:04AM +0000, Colin Watson wrote:
> > > + textdomain ("grub");
> >
> > What's the usual way to handle this? TEXTDOMAIN macro?
>
> I usually use textdomain (PACKAGE).
It's a bit unusual that we don't have PACKAGE. This is usually provided
by aclocal via AM_INIT_AUTOMAKE(), so I guess it's time to start
auto-generating aclocal.m4, as with attached patch.
Comments?
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
2009-11-16 Robert Millan <[email protected]>
* aclocal.m4: Move from here ...
* acinclude.m4: ... to here.
* autogen.sh: Add call to `aclocal'.
* configure.ac: Add AM_INIT_AUTOMAKE() after AC_INIT() call.
=== renamed file 'aclocal.m4' => 'acinclude.m4'
=== modified file 'autogen.sh'
--- autogen.sh 2009-11-08 16:43:36 +0000
+++ autogen.sh 2009-11-16 19:01:50 +0000
@@ -2,6 +2,7 @@
set -e
+aclocal
autoconf
autoheader
echo timestamp > stamp-h.in
=== modified file 'configure.ac'
--- configure.ac 2009-11-09 19:58:24 +0000
+++ configure.ac 2009-11-16 19:00:41 +0000
@@ -32,6 +32,7 @@ dnl type.
AC_INIT([GRUB],[1.97],[[email protected]])
+AM_INIT_AUTOMAKE()
AC_PREREQ(2.59d)
AC_CONFIG_SRCDIR([include/grub/dl.h])
AC_CONFIG_HEADER([config.h])
_______________________________________________
Grub-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/grub-devel