On Fri, Jan 04, 2013 at 09:35:37AM +0100, Matthias Andree wrote:
Oh, it does, albeit to a subdirectory below the build directory - that
is one of the purposes: check if it "make install"/"make uninstall"
unduly leaves residues...
Thanks, I didn't read the entire section, and I see it does
mention it near the bottom of that section.
Here is what is generated in the Makefile:
&& ../configure --srcdir=.. --prefix="$$dc_install_base" \
$(AM_DISTCHECK_CONFIGURE_FLAGS) \
$(DISTCHECK_CONFIGURE_FLAGS) \
The problem I see with hardcoding AM_DISTCHECK_CONFIGURE_FLAGS
with any particular option is that since it is not possible to
override that option, any other developer trying to use this
functionality to test builds with a different feature set is
stuck. This is similar to the sitatuion where the user of the
configure script must specify non-default options for their
situation.
If you need it for some reason:
The user can still extend or override the flags
provided there by defining the `DISTCHECK_CONFIGURE_FLAGS' variable, on
the command line when invoking `make'.
I know this is possible, but I have seen "make distcheck" failures when
run without sudo due to chgrp failing.
If you are seeing install failures when the chmod/chgrp is not required,
please file a bug and I will look into that.
