This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

cvs update


Bob Rossi writes:
 > Hi,
 > 
 > When doing a 'cvs update' do I have to do it from the top level?
 > or can I do it from src/gdb?

You _could_ do it from either, but obviously if you do it in
src/gdb you're not going to update any sibling directories
like bfd or include.

 > I don't know if gdb depends on binutils, ... for running on the host.

"Binutils" is ambiguous, unfortunately.  Assuming you mean the src/binutils
directory then "no", gdb doesn't need anything in there.
If you mean the various pieces that make up the binutils package
(e.g. binutils-2.14) then "sorta", both contain directories
bfd,include,opcodes which both need.
If built separately each would have their own copies of these dirs.
If one has checked out both gdb and binutils into a common tree
then they both share these dirs.

 > If I do need to update several packages, is there a list? or should I
 > just do it from the top level?

The problem with doing a cvs update is that it won't bring in
new directories by default.  Generally there are none, but
it does happen.
You can fix this by adding the -d parameter (cvs update -d) but you DON'T
want to do that at the top level because it will drag in
every other sibling directory of gdb, even ones not part of the
modules you originally checked out.

One s.o.p. is to checkout a module and then always update the same
way as you checked out.
That way you always update all the dependencies as a matter of course.

i.e. if you did you're cvs checkout with:

bash$ cvs -d ':pserver:anoncvs@sources.redhat.com:/cvs/src' checkout gdb

then always updated the same way:

bash$ cvs -d ':pserver:anoncvs@sources.redhat.com:/cvs/src' checkout gdb

(and remember to run the second checkout in the parent of src of course).
Or, if you checked out both gdb and binutils, say with:

bash$ cvs -d ':pserver:anoncvs@sources.redhat.com:/cvs/src' checkout gdb binutils

then, again, update the same way:

bash$ cvs -d ':pserver:anoncvs@sources.redhat.com:/cvs/src' checkout gdb binutils


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]