--- Begin Message ---
|
Subject: |
distclean failure with Automake 1.12.2 |
|
Date: |
Fri, 27 Jul 2012 12:12:30 +1000 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:10.0.6esrpre) Gecko/20120714 Thunderbird/10.0.6 |
Hi automakers,
I was about to make a release when I discovered that distcheck suddenly
didn't work anymore. The distclean rule failed with
Making distclean in doc
make[2]: Entering directory
`/home/peterJo/projects/software/yat-0.8.x/yat-0.8.2/_build/doc'
Makefile:498: ../yat/classifier/doxygen.mk: No such file or directory
Makefile:499: ../yat/normalizer/doxygen.mk: No such file or directory
This was for a stable branch release so there had just been minor
changes in two .cc files and no changes at all wrt the build system.
After some investigation I found that Automake 1.12.2 has changed the
order directories are traversed for clean rules. I must say I find it
unexpected that behaviour like this is changed between 1.12.1 and
1.12.2. I thought this kind of changes were only introduced when bumping
versions from say 1.11 to 1.12 and not between stable releases.
The reason I got the failure is that files doxygen.mk are included into
doc/Makefile. These files are generated in the corresponding Makefile
and listed under DISTCLEANFILES so they are deleted during 'make
distclean'. As SUBDIRS in top Makefile.am is SUBDIRS = doc yat that was
not a problem before since doc was entered first during cleaning and
doc/Makefile was already gone when the doxygen.mk files were removed.
Perhaps a strange use case, but still I wanted to report it.
I think I've found a workaround so I can get out the release without
needing to downgrade Automake.
Thanks,
Peter
--- End Message ---
--- Begin Message ---
|
Subject: |
Re: bug#12064: distclean failure with Automake 1.12.2 |
|
Date: |
Wed, 21 Nov 2012 10:51:31 +0100 |
Reference:
<http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12064>
Since I've seen no further reports of similar problems, and since we
have concluded the issue in question wasn't due to an Automake bug,
but rather to a legitimate-but-slightly-backward-incompatible change
in Automake's behaviour (change that I stupidly introduced in a minor
version, rather than in a major version as it would have been
appropriate -- sorry again about that), I'm closing this bug report.
If anybody has further observations or objections, feel free to
continue the discussion here; that should still be possible even
if the bug has been closed.
Thanks,
Stefano
--- End Message ---