-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Bruno Haible on 8/23/2006 6:03 AM: > Hi, > > Up to now, gl_LOCK must be placed as the last element of gl_EARLY, and > no other macros that modify LIBS or CPPFLAGS can be used after gl_LOCK. > To resolve these weird constraints, I'm separating the "early" part of > the macro (which can modify LIBS or CPPFLAGS) from the "normal" part > (which tests for features, using LIBS and CPPFLAGS).
Unfortunately, this is now giving me the following when bootstrapping m4: during gnulib-tool update: Updating file ltdl/m4/lock.m4 (backup in ltdl/m4/lock.m4~) during autoreconf -fv autoreconf: running: autopoint --force ... Copying file ltdl/m4/lock.m4 ... configure.ac:104: warning: gl_LOCK_EARLY is m4_require'd but not m4_defun'd ltdl/m4/gnulib-comp.m4:28: M4_EARLY is expanded from... configure.ac:104: the top level autoreconf: running: /usr/local/bin/autoconf --force configure.ac:104: warning: gl_LOCK_EARLY is m4_require'd but not m4_defun'd ltdl/m4/gnulib-comp.m4:28: M4_EARLY is expanded from... configure.ac:104: the top level configure:4868: error: possibly undefined macro: gl_LOCK_EARLY If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. autoreconf: /usr/local/bin/autoconf failed with exit status: 1 What is the recommended approach to use gnulib's lock.m4 instead of gettext 0.15's? - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE7xo+84KuGfSFAYARAhALAJkBffsFGBfmdmA5NuVSCTRWhaQgKQCfQ5Mx C0q8KSkwoRZ1evWQWHViTUo= =1Lqj -----END PGP SIGNATURE-----