[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cvs update from head doesn't seem to work

From: Rod Butcher
Subject: Re: cvs update from head doesn't seem to work
Date: Tue, 22 Nov 2005 15:29:42 +1100
User-agent: Mozilla Thunderbird 1.0.7 (X11/20050923)

Russ Sherk wrote:

On 11/19/05, *Rod Butcher* <address@hidden <mailto:address@hidden>> wrote:

    I maintain a working copy of Gnome from cvs head, which I update and
    recompile periodically to help with beta testing.
    It appears that new headers etc get downloaded ok, but often code
    changes don't get made in "update" mode, resulting in compile errors -
    if I checkout the whole module again I get a clean copy which
    compiles ok.
    my checkout command :-
    cvs -d :pserver:address@hidden/cvs/gnome
    <http://pserver:address@hidden/cvs/gnome> checkout nautilus

Do you check out over top of an existing copy or do you rm -rf; cvs co?
    my update command :-
    cvs -d : pserver:address@hidden/cvs/gnome
    <http://pserver:address@hidden/cvs/gnome> update -dP

    but this doesn't always pick up latest changes from head. ???
    thanks for any pointers

It should. Some build systems re-write config files and some sources. When you do your cvs up, do you notice any cvs markers like M or C. This would indicate modified sources (presumabljy modified by the build). If so, try to corrolate the modified or conflicting files with the build errors.
Thanks for the build pointer...
I just discovered that the problem does not occur if I run autogen every time before the compile.. previously I was only running autogen after the initial checkout. Do you guys always run autogen after updating from cvs ? (gnome includes for this).

Another thing to try is: make clean; make distclean; ./configure; make (this is generic. I have never looked at the gnome build)


    <corporate disclaimer drivel goes here>

    Info-cvs mailing list
    address@hidden <mailto:address@hidden>

<corporate disclaimer drivel goes here>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]