From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5287 invoked by alias); 16 Sep 2008 18:27:34 -0000 Received: (qmail 5279 invoked by uid 22791); 16 Sep 2008 18:27:32 -0000 X-Spam-Check-By: sourceware.org Received: from smtp-outbound-1.vmware.com (HELO smtp-outbound-1.vmware.com) (65.113.40.141) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 16 Sep 2008 18:26:58 +0000 Received: from mailhost2.vmware.com (mailhost2.vmware.com [10.16.64.160]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id 4C3606977; Tue, 16 Sep 2008 11:26:56 -0700 (PDT) Received: from [10.20.92.218] (promb-2s-dhcp218.eng.vmware.com [10.20.92.218]) by mailhost2.vmware.com (Postfix) with ESMTP id 1DA288E590; Tue, 16 Sep 2008 11:26:56 -0700 (PDT) Message-ID: <48CFF9FE.701@vmware.com> Date: Tue, 16 Sep 2008 18:27:00 -0000 From: Michael Snyder User-Agent: Thunderbird 1.5.0.12 (X11/20080411) MIME-Version: 1.0 To: "jeremy.bennett@embecosm.com" CC: "gdb@sourceware.org" Subject: Re: Problem (and solution) building from CVS References: <1221571471.2827.324.camel@thomas> <20080916150138.GA22292@caradoc.them.org> <1221583603.2827.345.camel@thomas> <20080916172102.GA30290@caradoc.them.org> <1221587655.2827.356.camel@thomas> In-Reply-To: <1221587655.2827.356.camel@thomas> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-09/txt/msg00108.txt.bz2 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.