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 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. I guess it is about the 'make dist' functionality. All
others
like 'make distclean' etc. are only assisting functionality for
'make dist'
after all.
And for 'make dist' you need to have everything configured that is
going to be
part of the distribution. Therefore, VT needs to be part of the
tarball, so
you can disable it at build time. It would not work the other way
around.
So in my opinion, the current status is what we want to have. Are
there any
problems when configuring VT, then building the tarball with VT and
disabling
it once you build Open MPI from the tarball?
Regards, Andreas
--
Dipl. Math. Andreas Knuepfer,
Center for Information Services and
High Performance Computing (ZIH), TU Dresden,
Willersbau A114, Zellescher Weg 12, 01062 Dresden
phone +49-351-463-38323, fax +49-351-463-37773
_______________________________________________
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel
