Fri 15 Apr 2016 11:05:37 AM UTC, comment #2:
If the Windows build uses autoconf, it should be OK. According to the manual it will create a copy if symlinks aren't available:
Are there are any instructions for creating the Windows binaries? I'd be happy to test it out if so.
|
Tue 12 Apr 2016 10:31:05 AM UTC, original submission:
Steps to reproduce:
1. Fresh checkout from CVS as of 2016-04-07
2. ./autogen.sh
3. ./configure
4. make distclean
Expected:
All files created at step 3 should be removed
Actual:
Errors of the form 'Makefile:802: .deps/analysis.Po: No such file or directory', and a few files left behind.
Tool versions:
automake 1.15, autoconf 2.69, make 4.1
Analysis:
The lib submake builds ../output.c in place, making use of ../$(DEPDIR) to do so. Automake therefore generates this distclean rule in lib/Makefile:
distclean: distclean-am
-rm -rf ../$(DEPDIR) ./$(DEPDIR)
When the lib submake completes, control returns to the top-level makefile, which fails on a string of 'include ./$(DEPDIR)/*' directives because the directory has been deleted.
Would it be acceptable to symlink output.c into the lib subdir during configuration instead of building it in place?
Or, feel free to tell me to mind my own business, I'm new around here :)
|