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.