we discussed this issue here a lot. Indeed, we were putting the contents of
the VampirTrace tarball to the trunk (via the vendor branch stuff).
Then again, this is no virtue by itself, is it? So we agree to removing the
configure scripts from the SVN and having it created by the autogen script.
This might resolve possible problems because of differing autoconf versions
See/hear you at the telco, Andreas
On Friday 01 February 2008, Jeff Squyres wrote:
> On Feb 1, 2008, at 5:35 AM, Ralf Wildenhues wrote:
> > These files do not belong in SVN, they are generated by aclocal:
> > ompi/contrib/vt/vt/extlib/otf/aclocal.m4
> > ompi/contrib/vt/vt/aclocal.m4
> I think both of these have their own configure scripts, meaning that
> they were autoconfed/automaked/whatever before they were put into OMPI.
> And in hindsight, this fits in with exactly what our original goal
> was: take a VT tarball and dump it into OMPI's SVN. Doh!
> So I think the question still remains: can we hook VT's autoconf (et
> al.) requirements into the top-level autogen.sh so that the trunk copy
> of vt doesn't have configure/aclocal.m4/etc. and OMPI's top-level
> autogen.sh will create them?
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