Re: bug with `make dist' and `AC_CONFIG_LINKS'

[Thomas Schwinge]

Hello!

On Wed, Nov 29, 2006 at 06:01:11PM +0100, Ralf Wildenhues wrote:
> * Thomas Schwinge wrote on Wed, Nov 29, 2006 at 03:11:43PM CET:
> > 
> > It seems to me that all files from directories that are referenced within
> > an `AC_CONFIG_LINKS' rule in the `configure.ac' file will automatically
> > selected to be included in the tarball the `make dist' creates, even
> > those that live in the build-directory!
> 
> In portable projects, AC_CONFIG_LINKS cannot be used with directories as
> source, as it may try to hard-link them:
> http://www.gnu.org/software/autoconf/manual/html_node/Configuration-Links.html

Hm.

> However, if you know `ln -s' works, then, according to this comment in
> automake.in:handle_configure:
>       # Some people do AC_CONFIG_LINKS($computed).  We only handle
>       # the DEST:SRC form.
> 
> you should be able to use the following workaround (untested):
>    machlink=machine:${systype}/${systype}
>    AC_CONFIG_LINKS([$machlink])

That wasn't even needed, see below.

> plus putting the needed files in EXTRA_DIST of course.  The manual
> contains some rationale about AC_CONFIG_FILES that seems to apply
> likewise to AC_CONFIG_LINKS (see at the end of the section):
> http://sources.redhat.com/automake/automake.html#Requirements

_That one_ was the crucial hint, so thanks for this pointer, Ralf!

#v+
[...]
# Use `$file' (or `${file}' without `AC_SUBST([file])') for files that automake 
should ignore.
# Use `${file}' and `AC_SUBST([file])' for files that automake should not 
ignore. 
[...]
#v-

Changing ``AC_CONFIG_LINKS([machine:${systype}/${systype}])'' to
``AC_CONFIG_LINKS([machine:$systype/$systype])'' my problem was solved!


I'll try to think about it some more and then post a patch to update the
documentation or some further ideas about how this could be handled.


Regards,
 Thomas

signature.asc
Description: Digital signature