| Following the suggestions in the manual, I create a rule like
| GNUmakefile: GNUmakefile.in $(top_builddir)/config.status
| cd $(top_builddir) && CONFIG_FILES=$@ CONFIG_HEADERS= ./config.status
|
| to automatically rebuild the makefiles. The above won't work in a
| subdirectory, so how about
|
| GNUmakefile: GNUmakefile.in $(top_builddir)/config.status
| CONFIG_FILES=$@ CONFIG_HEADERS= $(top_builddir)/config.status
|
| That works okay as far as re-creating the makefile is concerned, but for
| some reason config.status also recreates all AC_LINK_FILES at that time
| (why?), which fails:
Why? Because you didn't set CONFIG_LINKS to nothing :) This is CVS
only.
| $ CONFIG_FILES=GNUmakefile CONFIG_HEADERS= ../../config.status
| creating GNUmakefile
| linking ./src/backend/port/dynloader/linux.c to src/backend/port/dynloader.c
| configure: error: ./src/backend/port/dynloader/linux.c: File not found
Yep, config.status *must* be run from ./
| GNUmakefile: GNUmakefile.in $(top_builddir)/config.status
| dir=`pwd` && cd $(top_builddir) && \
| CONFIG_FILES=$$dir/$@ CONFIG_HEADERS= ./config.status
|
| but it's already ugly as it is. Is this addressed in the development
| version?
If you're using CVS Autoconf, drop the �"(*$& syntax dead, and to move
to
GNUmakefile: GNUmakefile.in $(top_builddir)/config.status
cd $(top_builddir) && ./config.status $(subdir)/$@
Using subdir = lib or whatever is more beautiful :)
No, the CVS version does not improve any further the interface. We
might accept patches, but we won't work on it soon :(
Akim
