On 11/19/05, Rod Butcher <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
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 update -dP nautilus
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.
Another thing to try is: make clean; make distclean; ./configure; make
(this is generic. I have never looked at the gnome build)
--Russ
Rod
-----------------------------------------------------
<corporate disclaimer drivel goes here>
_______________________________________________
Info-cvs mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/info-cvs