Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Development mailing list

Subject: Re: [OMPI devel] Something wrong with vt?
From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2008-02-12 09:37:17


autogen.sh has some deep mojo in it...

Would it be sufficient to just have our autogen.sh recurse down into
your tree? An undocumented feature of our autogen.sh is that you can
have a "autogen.subdirs" file in ompi/contrib/vt with a single line in
it: "vt". This will make our autogen recurse into the vt ompi/contrib/
vt/vt tree and run all of its magic in there.

I say this with only a *very quick* look elsewhere in the tree; it
works in the MCA frameworks (e.g., ompi/mca/io/romio) -- I have not
checked to see if it'll work in the contrib area; we may need to
expand the logic a bit there (i.e., copy over what was done for
autogen.subdirs elsewhere). Can you investigate this possibility?

Matthias: can you please login to trac and set your e-mail address to
that I can assign ticket #1212 to you? Use your SVN username and
password. Thanks.

On Feb 12, 2008, at 8:04 AM, Matthias Jurenz wrote:

> In future all Makefile.in's and the configure script of VT will be
> built from OMPI's autogen.sh.
> I'm working on a solution, but the autogen.sh script is a little bit
> unclear for me... :-(
>
> Matthias
>
>
> On Di, 2008-02-12 at 14:37 +0200, Gleb Natapov wrote:
>>
>> On Tue, Feb 12, 2008 at 01:08:32PM +0100, Matthias Jurenz wrote:
>> > Hi Gleb,
>> >
>> > that's very strange... cause' the corresponding 'Makefile.in' is
>> > definitely not empty (checked in to the SVN repository).
>> Ah, here is the problem. Makefile.in is empty in my tree. I am
>> building
>> not from SVN checkout, but from the other source tree that is synced
>> with SVN checkout and the sync process consider Makefile.in files as
>> generated and ignores them. Why Makefiles.in is not regenerated by
>> autogen.sh in vt sources?
>>
>>
>> > Could you reproduce this error after 'make distclean, configure,
>> make' ?
>> > Which version of the autotools are you using?
>> >
>> >
>> > Matthias
>> >
>> > On Mo, 2008-02-11 at 11:42 +0200, Gleb Natapov wrote:
>> >
>> > > I get the following error while "make install":
>> > >
>> > > make[2]: Entering directory `/home_local/glebn/build_dbg/ompi/
>> contrib/vt'
>> > > Making install in vt
>> > > make[3]: Entering directory `/home_local/glebn/build_dbg/ompi/
>> contrib/vt/vt'
>> > > make[3]: *** No rule to make target `install'. Stop.
>> > > make[3]: Leaving directory `/home_local/glebn/build_dbg/ompi/
>> contrib/vt/vt'
>> > > make[2]: *** [install-recursive] Error 1
>> > > make[2]: Leaving directory `/home_local/glebn/build_dbg/ompi/
>> contrib/vt'
>> > > make[1]: *** [install-recursive] Error 1
>> > > make[1]: Leaving directory `/home_local/glebn/build_dbg/ompi'
>> > > make: *** [install-recursive] Error 1
>> > >
>> > > ompi/contrib/vt/vt/Makefile is empty!
>> > > --
>> > > Gleb.
>> > > _______________________________________________
>> > > devel mailing list
>> > > devel_at_[hidden]
>> > > http://www.open-mpi.org/mailman/listinfo.cgi/devel
>> > >
>> >
>> > --
>> > Matthias Jurenz,
>> > Center for Information Services and
>> > High Performance Computing (ZIH), TU Dresden,
>> > Willersbau A106, Zellescher Weg 12, 01062 Dresden
>> > phone +49-351-463-31945, fax +49-351-463-37773
>>
>>
>>
>> > _______________________________________________
>> > devel mailing list
>> > devel_at_[hidden]
>> > http://www.open-mpi.org/mailman/listinfo.cgi/devel
>>
>> --
>> Gleb.
>> _______________________________________________
>> devel mailing list
>> devel_at_[hidden]
>> http://www.open-mpi.org/mailman/listinfo.cgi/devel
>>
> --
> Matthias Jurenz,
> Center for Information Services and
> High Performance Computing (ZIH), TU Dresden,
> Willersbau A106, Zellescher Weg 12, 01062 Dresden
> phone +49-351-463-31945, fax +49-351-463-37773
> _______________________________________________
> devel mailing list
> devel_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/devel

-- 
Jeff Squyres
Cisco Systems