-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 8/25/2006 10:20 AM:
>> What is the recommended approach to use gnulib's lock.m4 instead of
>> gettext 0.15's?
>
> Running autopoint _before_ gnulib-tool, so that gnulib-tool's newer
> files will overwrite those from gettex
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 8/25/2006 10:20 AM:
>
> Running autopoint _before_ gnulib-tool, so that gnulib-tool's newer
> files will overwrite those from gettext, appears to work better.
Thanks, I installed that with minor changes. Maybe it is time
Eric Blake wrote:
> 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
>
> ..
-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 separa
Bruno Haible <[EMAIL PROTECTED]> writes:
> 2006-08-23 Bruno Haible <[EMAIL PROTECTED]>
>
> * m4/lock.m4 (gl_LOCK_EARLY): Renamed from gl_LOCK.
Thanks for the heads-up. I installed the patch below to coreutils to
accommodate this.
This leads to one of the issues I had when converting core
