Re: Fix chdir-long.m4 caching

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Ralf Wildenhues on 10/1/2007 12:16 PM:
> Ahh, now I remember why I postponed that.  With a package using CVS HEAD
> Libtool:
> 
> | configure.ac:1001: warning: 
> AC_CACHE_VAL(_LT_TAGVAR(lt_prog_compiler_pic_works, ), ...): suspicious 
> cache-id, must contain _cv_ to be cached
> 
> Bugs in both Autoconf and Libtool (the error messages seem a bit
> inconsistent)?

I'm not sure I follow what you think is the Autoconf bug?  But yes, I
agree that libtool is certainly not caching what it was trying to do.

> 
> I guess branch-1-5 Libtool is affected just as well, and I wonder
> whether, if we rename variables in Libtool, we need to provide the old
> names for compatibility as well.

Nah.  They're cache variables; when they had the wrong name, the user
could feasibly override the check, but the override was not saved between
runs.  I think we're okay just upgrading to use new names, without
worrying about priming the new names from the value of the old, nor in
propagating the result of the new name back to the old, unless we can
prove that the old name was in use elsewhere.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHAjVs84KuGfSFAYARAqgKAJoCtYDOEmHxQ0SyKlW+JEXT68kjdQCgti+Z
DW+pU1xCezXvcBk8SPDyqa0=
=1TCM
-----END PGP SIGNATURE-----