Hmm; I'm not sure.
distclean will fail in a tarball or SVN checkout if you do --enable-
contrib-no-build=vt. So it's not a developer-only artifact.
I don't know what the Right solution is, though. :-\
On Feb 12, 2008, at 9:22 AM, Josh Hursey wrote:
Good points about 'distclean' versus '
Good points about 'distclean' versus 'clean'. For the make distclean
case then I think it is ok if we fail here since it is not a full
'make dist' that I was working with originally.
Sorry for the distraction.
Cheers,
Josh
On Feb 12, 2008, at 6:52 AM, Andreas Knüpfer wrote:
On Monday 11 F
On Monday 11 February 2008, Josh Hursey wrote:
> I've been noticing another problem with the VT integration. If you do
> a "./configure --enable-contrib-no-build=vt" a subsequent 'make
> distclean' will fail in contrib/vt. The 'make distclean' will succeed
> with VT enabled (default).
>
hm, tricky
* Josh Hursey wrote on Mon, Feb 11, 2008 at 07:31:25PM CET:
> I've been noticing another problem with the VT integration. If you do
> a "./configure --enable-contrib-no-build=vt" a subsequent 'make
> distclean' will fail in contrib/vt. The 'make distclean' will succeed
> with VT enabled (defa
I've been noticing another problem with the VT integration. If you do
a "./configure --enable-contrib-no-build=vt" a subsequent 'make
distclean' will fail in contrib/vt. The 'make distclean' will succeed
with VT enabled (default).
---
Making distclean in contrib/vt
make
