Harlan Stenn <[EMAIL PROTECTED]> writes:
> I'm generating a site-local file during configure that I use in
> AC_CONFIG_FILES.
> 
> The filename is in the $GUTS variable, and I create the target via:
> 
>  GUTS=$build_cpu-localname
>  echo stuff > $GUTS
>  AC_CONFIG_FILES([foo:foo-top.in:$GUTS:foo-bot.in])

Would AC_SUBST_FILE be more appropriate?  Do you have any @...@
substitutions in $GUTS that can't be done otherwise.
 
> Also, automake detects:
> 
>  harlan@bali> gmake
>  cd . && /bin/sh /home/harlan/src/foo/missing --run automake --foreign Makefile
>  configure.in: 74: required file `./$GUTS' not found
> 
> What's a good way to solve this problem?

Well, the AC_CONFIG_FILES are the set of files that automake
automatically generates config.status rules for.  If you can stand
writing Makefile.am rules instead, you can remove the $GUTS config
file from AC_CONFIG_FILES and use:

  EXTRA_DIST += foo-top.in foo-bot.in
  foo: $(srcdir)/foo-top.in $(GUTS) $(srcdir)/foo-bot.in config.status
        CONFIG_HEADERS= CONFIG_FILES=foo:foo-top.in:$(GUTS):foo-bot.in \
        $SHELL ./config.status

or a more readable command with a beta autoconf (2.49a):

  $SHELL ./config.status --file=foo:foo-top.in:$(GUTS):foo-bot.in

- Hari
-- 
Raja R Harinath ------------------------------ [EMAIL PROTECTED]
"When all else fails, read the instructions."      -- Cahn's Axiom
"Our policy is, when in doubt, do the right thing."   -- Roy L Ash

Reply via email to