Has anyone else seen this problem? When building current 7.7 from scratch, it bombs out during the configuration of CommonLog:
configure: loading cache ../.././config.cache configure: error: `LIBS' was not set in the previous run configure: error: changes in the environment can compromise the build
In config.cache there is the following:
ac_cv_env_LIBS_set= ac_cv_env_LIBS_value=
(these are the only ac_env/ac_cv_env entries). Maybe this is related to the line
LIBS=
in PIKE_RETAIN_VARIABLES somehow? Interestingly enough, the problem does not occur on my PS3, which also has
ac_cv_env_LIBS_set= ac_cv_env_LIBS_value=
in config.cache...
Looks like you need to add some more entries to the pollution filter in aclocal.m4:AC_OUTPUT (line ~733 - ~748).
Yes, it seems like this lists all the "precious vars" _except_ LIBS. Interresting omission...
Anyway the precious variable stuff breaks the support for chained configure scripts in combination with config.cache.
Henrik Grubbstr?m (Lysator) @ Pike (-) developers forum wrote:
Anyway the precious variable stuff breaks the support for chained configure scripts in combination with config.cache.
Was this ever (re)solved? Because it seems like the problem is still there in the current CVS version.
Yes, it seems like this lists all the "precious vars" _except_ LIBS. Interresting omission...
Looks like you need to add some more entries to the pollution filter in aclocal.m4:AC_OUTPUT (line ~733 - ~748).
pike-devel@lists.lysator.liu.se