Re: Toplevel configure script

Rob Crittenden wrote:
> You're using Elmer Fudd's GetWineX script for updating an existing CVS tree
> aren't you?

Ehh?  What is that?  I'm not using anybody's scripts, I'm just doing a:

cvs -z3 -d`cat CVSROOT` co wine

to check it out (CVSROOT is a file containing the CVS root, basically so
I don't forget it), and then a:

cvs up configure

from inside the tree to look at the newest configure.  I usually "cvs 
-z3 up -Pd" from inside the tree to grab the latest version of everything.

> There have been lots of reports of this problem on IRC. So far
> people have fixed them by manually fixing the merge issue.
> 

Does rerunning autoconf usually work for anybody else?

> It may be easier to do:
> 
> % mv configure configure.old
> % cvs update configure
> 

Doesn't help.  After I try, diff reports no changes (which makes sense,
since I'm doing the same thing ;-)).

> Or just check out and build a brand new tree.
> 

Tried that before I posted.  I just tried it again anyway, and no go.
:-(

Oh, crap, that's probably it.   I just realized I've been checking out
from cvs.winex.sourceforge.net, not cvs.transgaming.org (and I'm
checking out wine, not winex -- I never changed my CVSROOT file when the
CVS repository moved).  Which probably means it's the ancient tree.

Why don't I try again with the right cvsroot... (duh...)

Yep, that works just fine.  Sorry about the noise... :-o