John R Pierce <pierce@hogranch.com> writes:
> can someone confirm, the critical files that get customized by
> ./configure are
> $INCLUDEDIR/pg_config.h
> $INCLUDEDIR/server/pg_config.h (apparently identical)
> $LIBDIR/pgxs/src/Makefile.global
I believe all of the files that get written at the end of configure are
potentially architecture-sensitive. There are at least two other .h
files that qualify: ecpg_config.h and pg_config_os.h (the latter is a
symlink). A quick look through configure.in shows these files getting
made:
AC_CONFIG_LINKS([src/backend/port/tas.s:src/backend/port/tas/${tas_file}])
AC_CONFIG_FILES([GNUmakefile src/Makefile.global])
AC_CONFIG_LINKS([
src/backend/port/dynloader.c:src/backend/port/dynloader/${template}.c
src/backend/port/pg_sema.c:${SEMA_IMPLEMENTATION}
src/backend/port/pg_shmem.c:${SHMEM_IMPLEMENTATION}
src/include/dynloader.h:src/backend/port/dynloader/${template}.h
src/include/pg_config_os.h:src/include/port/${template}.h
src/Makefile.port:src/makefiles/Makefile.${template}
])
AC_CONFIG_HEADERS([src/include/pg_config.h],
[
# Update timestamp for pg_config.h (see Makefile.global)
echo >src/include/stamp-h
])
AC_CONFIG_HEADERS([src/interfaces/ecpg/include/ecpg_config.h],
[echo >src/interfaces/ecpg/include/stamp-h])
The .c files are probably not relevant for building add-on modules, but
I think all the others are.
regards, tom lane
