Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > GNUmakefile: GNUmakefile.in $(top_builddir)/config.status
> > dir=`pwd` && cd $(top_builddir) && \
> > CONFIG_FILES=$$dir/$@ CONFIG_HEADERS= ./config.status
>
> Okay, that won't work either:
>
> dir=`pwd` && cd ../../.. && CONFIG_FILES=$dir/GNUmakefile CONFIG_HEADERS=
>./config.status
> creating /home/peter/pgsql/src/interfaces/perl5/GNUmakefile
> sed: can't read .//home/peter/pgsql/src/interfaces/perl5/GNUmakefile.in: No such
>file or directory
>
> So now the question is really: how *do* you invoke config.status from a
> subdirectory at all?
I think you have to do:
cd $(top_builddir) && \
CONFIG_FILES=$(subdir)/$@ CONFIG_HEADERS= ./config.status
where subdir is the relative path from the top to the current
directory. As for setting subdir, either you do it yourself or you
have automake do it.
/assar
