New issue 53 by hartmut.holzgraefe: Warnings wen running autoreconf -vi
http://code.google.com/p/google-ctemplate/issues/detail?id=53
What steps will reproduce the problem?
1. run "autoreconf -vi" in top level directory
What is the expected output?
* progress messages without warnings
What do you see instead?
* several warnings:
configure.ac:65: warning: AC_CACHE_VAL(ac_rwlock, ...): suspicious
cache-id, must contain _cv_ to be cached
../../lib/autoconf/general.m4:2018: AC_CACHE_VAL is expanded from...
../../lib/autoconf/general.m4:2039: AC_CACHE_CHECK is expanded from...
m4/ac_rwlock.m4:21: AC_RWLOCK is expanded from...
[...]
libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac
and
libtoolize: rerunning libtoolize, to keep the correct libtool macros
in-tree.
[...]
Makefile.am:334: compiling `statemachine_test.c' with per-target flags
requires `AM_PROG_CC_C_O' in `configure.ac'
[...]
What version of the product are you using?
* reproduced in both 0.96 and todays SVN (2010-01-22)
On what operating system?
* Ubuntu Linux 9.10
Please provide any additional information below.
* see attached file for proposed patch
Attachments:
patch 1.4 KB
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
Autotools versions:
autoconf (GNU Autoconf) 2.64
automake (GNU automake) 1.11
ltmain.sh (GNU libtool) 2.2.6
Comment #2 on issue 53 by csilvers: Warnings wen running autoreconf -vi
http://code.google.com/p/google-ctemplate/issues/detail?id=53
Thanks for the report -- I've noticed this too, and will fix it up for the
next
release.