[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug with `make dist' and `AC_CONFIG_LINKS'
From: |
Thomas Schwinge |
Subject: |
bug with `make dist' and `AC_CONFIG_LINKS' |
Date: |
Wed, 29 Nov 2006 15:11:43 +0100 |
User-agent: |
Mutt/1.5.9i |
Hello!
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!
E.g. I have ``AC_CONFIG_LINKS([machine:${systype}/${systype}])'' in
`configure.ac'. `systype' is set to `i386' at that point. What I want
to achieve with that is having a link `[build]/machine' pointing to
`[source]/i386/i386' -- which is working, of course. But when I now do a
`make dist', `[distdir]/i386/i386/' will now contain the files from
`[source]/i386/i386/' -- as expected -- but also those from
`[build]/i386/i386/' -- which is not expected, as those are the compiled
object files and other files that are generated during the build.
I hope this analysis if correct. Does it suffice or do you need a real
test case?
Regards,
Thomas
signature.asc
Description: Digital signature
- bug with `make dist' and `AC_CONFIG_LINKS',
Thomas Schwinge <=