From: Michael Snyder <msnyder@vmware.com>
To: "jeremy.bennett@embecosm.com" <jeremy.bennett@embecosm.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Problem (and solution) building from CVS
Date: Tue, 16 Sep 2008 18:27:00 -0000 [thread overview]
Message-ID: <48CFF9FE.701@vmware.com> (raw)
In-Reply-To: <1221587655.2827.356.camel@thomas>
Jeremy Bennett wrote:
> On Tue, 2008-09-16 at 13:21 -0400, Daniel Jacobowitz wrote:
>> On Tue, Sep 16, 2008 at 05:46:43PM +0100, Jeremy Bennett wrote:
>>> On Tue, 2008-09-16 at 11:01 -0400, Daniel Jacobowitz wrote:
>>>> On Tue, Sep 16, 2008 at 02:24:31PM +0100, Jeremy Bennett wrote:
>>>>> I ran into problems building from the CVS tree earlier today. I checked
>>>>> out the GDB tree using:
>>>>>
>>>>> cvs -d :pserver:anoncvs@sourceware.org:/cvs/src co gdb
>>>> This command should not get you gdb/gdbtk. It doesn't when I check it
>>>> out. DId you cvs up -dP later on?
>>> Yes I did.
>> That's why. Update using the same command you used to check out, and
>> you won't get gdbtk (or a lot of other things not related to GDB).
>
> Hi Daniel,
>
> I'll use "cvs co", not "cvs update". Thanks for the explanation.
Update is fine, it's a question of what options.
The options Daniel named will cause update to pull in
stuff that was not originally checked out.
prev parent reply other threads:[~2008-09-16 18:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 13:25 Jeremy Bennett
2008-09-16 13:31 ` Andreas Schwab
2008-09-16 13:48 ` Jeremy Bennett
2008-09-16 17:15 ` Tom Tromey
2008-09-16 15:02 ` Daniel Jacobowitz
2008-09-16 16:47 ` Jeremy Bennett
2008-09-16 17:21 ` Daniel Jacobowitz
2008-09-16 17:55 ` Jeremy Bennett
2008-09-16 18:27 ` Michael Snyder [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48CFF9FE.701@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb@sourceware.org \
--cc=jeremy.bennett@embecosm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox