Page 1 of 1

Adding extension does not change configure script

Posted: Fri Sep 20, 2002 9:34 am
by lovasco
Dear folks,
I installed php 4.2.3 (fine) and added a new extension:

> ext_skel --extname=first_module

then I edited the config.m4 file to uncomment the enable option:

PHP_ARG_ENABLE(first_module, whether to enable first_module support,
[ --enable-first_module Enable first_module support])

and ran the buildconf script which generated the following output:

rebuilding configure
rebuilding main/php_config.h.in
WARNING: Using auxiliary files such as `acconfig.h', `config.h.bot'
WARNING: and `config.h.top', to define templates for `config.h.in'
WARNING: is deprecated and discouraged.
WARNING: Using the third argument of `AC_DEFINE' and
WARNING: `AC_DEFINE_UNQUOTED' allows to define a template without
WARNING: `acconfig.h':
WARNING: AC_DEFINE([NEED_MAIN], 1,
WARNING: [Define if a function `main' is needed.])
WARNING: More sophisticated templates can also be produced, see the
WARNING: documentation.
autoheader: `main/php_config.h.in' is created
Target "all" is up to date.

After running the buildconf script I found that the configure script did not change; in fact it should reflect all the config.m4 files in the ext/ subfolders.
All dependent packages are up to date:
- m4 1.4
- autoconf 2.53
- automake 1.6.3
- libtool 1.4

As a counterproof I moved the calendar folder to a different place and ran the buildconf again. No change; the configure --help still shows the calendar extension and does not chow the newly generated extension first_module.

Is there some file that needs to be removed in order for the buildconf script to work properly ? Some kind of config.cache ? (No use deleting the configure script).

Could you help me ?
Thanks,
Luca

Fixed

Posted: Fri Sep 20, 2002 11:04 am
by lovasco
I found out the problem can be easely fixed by clearing the autom4te.cache folder before re-running the buildconf script.
Bye

Posted: Fri Sep 20, 2002 12:05 pm
by jason
Sorry we couldn't help, but thanks for the heads up.