Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [OMPI devel] Is trunk broken ?
From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2008-06-20 06:53:30

On Jun 19, 2008, at 5:38 PM, Ralph Castain wrote:

>> If so, I wonder if what happened was that Pasha did an "svn up", but
>> without re-running autogen/configure, he wouldn't have seen the new
>> "bad" component and therefore was falling back on the old "basic"
>> component that is now the non-default / testing component...?
> Could be - though I thought that if you do a "make" in that
> situation, it
> would force a re-autogen/configure when it saw a new component?

No, it does not. The addition / removal of a component requires a
[manual] autogen/configure for the build system to see it.

Jeff Squyres
Cisco Systems