cvs update

cvs update

[Bob Rossi]

Hi,

When doing a 'cvs update' do I have to do it from the top level?
or can I do it from src/gdb?

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

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

Thanks,
Bob Rossi

cvs update

[Doug Evans]

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

cvs update

[Doug Evans]

Doug Evans writes:
 > Bob Rossi writes:
 >  > If I do need to update several packages, is there a list? or should I
 >  > just do it from the top level?
 > 
 > 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

Sorry to follow-up my own message.  I forgot something.

You can see what modules are available to checkout with

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

and browse file modules/modules.

Note that there is a combined gdb+binutils module, thus you can do:

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

Dunno how permanent the gdb+binutils module is.

Re: cvs update

[Bob Rossi]

wooo, I didn't know you could do that. Thanks!

It seems like your saying there are many ways to do it. It also seems
like you are saying to *not* just update the gdb tree. I have to update
everything it depends on?

I am new at working with gdb, sorry for the low level questions.

Thanks,
Bob Rossi


On Thu, Aug 07, 2003 at 08:22:10AM -0700, Doug Evans wrote:
> Doug Evans writes:
>  > Bob Rossi writes:
>  >  > If I do need to update several packages, is there a list? or should I
>  >  > just do it from the top level?
>  > 
>  > 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
> 
> Sorry to follow-up my own message.  I forgot something.
> 
> You can see what modules are available to checkout with
> 
> bash$ cvs -d ':pserver:anoncvs@sources.redhat.com:/cvs/src' checkout modules
> 
> and browse file modules/modules.
> 
> Note that there is a combined gdb+binutils module, thus you can do:
> 
> bash$ cvs -d ':pserver:anoncvs@sources.redhat.com:/cvs/src' checkout gdb+bintuils
> 
> Dunno how permanent the gdb+binutils module is.

Re: cvs update

[David Carlton]

On Thu, 7 Aug 2003 07:32:18 -0400, Bob Rossi <bob@brasko.net> said:

> When doing a 'cvs update' do I have to do it from the top level?
> or can I do it from src/gdb?

Most of the time, I do it from within src/gdb, but every few weeks I
do it from within src.

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

The GDB binary is self-contained.

David Carlton
carlton@kealia.com

Re: cvs update

[Doug Evans]

Bob Rossi writes:
 > It also seems
 > like you are saying to *not* just update the gdb tree. I have to update
 > everything it depends on?

That's a judgement call.
[pedantic: it's based on one's experience, what one is
currently working on, how many trees one has checked out, which
modules are in each tree, knowledge of changes that have gone in since
the last update, knowledge of what versions of installed tools
are in use, and I'm guessing various other things I'm forgetting.]

For the context of being fairly new to gdb, with just the
gdb module checked out, I would update everything in the gdb module
every time (using the way I previously showed).

[pedantic: even that could get one into trouble. As Michael points out,
various changes in other tools can cause problems.  If you're
on a fairly old linux system, for example, with a fairly old
binutils, for example, and you need support for something that's
only recently been fixed, you may find you have to either install
newer versions of those tools or start using a combined tree.
But if you're fairly new, I wouldn't worry about it at all. TMI.
Just file this away for future reference.]

 > I am new at working with gdb, sorry for the low level questions.

No problem.

Re: cvs update

[Michael Elizabeth Chastain]

> When doing a 'cvs update' do I have to do it from the top level?
> or can I do it from src/gdb?

See Daniel's message.

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

Basically, no.  You can just use binutils 2.14 and not update your
binutils until 2.14.1 comes out, and gdb will work fine, even if you
use a cvs version of gdb and update it every day.

Here's what I do.  I regularly test the cross product of these choices:

  gdb: 5.3, gdb_6_0-branch, HEAD
  gcc: 2.95.3, vendor, 3.3, gcc-3_3-branch, HEAD
  binutils: vendor, 2.14, binutils-2_14-branch, HEAD

(Yes, it's a lot of testing).

If there is a difference between different versions of binutils,
I'll see it and report it.  But starting with binutils 2.13.2.1,
basically all versions of binutils work the same almost all the time,
so you can just settle with one and forget about it.

My old vendor binutils doesn't support thread local storage but
that is the only difference I've seen.

Michael C