From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7144 invoked by alias); 7 Jul 2005 20:38:38 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 7088 invoked by uid 22791); 7 Jul 2005 20:38:26 -0000 Received: from e33.co.us.ibm.com (HELO e33.co.us.ibm.com) (32.97.110.131) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 07 Jul 2005 20:38:26 +0000 Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11]) by e33.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id j67KcMnf463380 for ; Thu, 7 Jul 2005 16:38:22 -0400 Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by westrelay02.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j67KcLAu329706 for ; Thu, 7 Jul 2005 14:38:21 -0600 Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.12.11/8.13.3) with ESMTP id j67KcLHp006338 for ; Thu, 7 Jul 2005 14:38:21 -0600 Received: from dyn9047022123-009047022128.beaverton.ibm.com (dyn9047022123-009047022128.beaverton.ibm.com [9.47.22.128]) by d03av02.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id j67KcL4e006313; Thu, 7 Jul 2005 14:38:21 -0600 From: Paul Gilliam Reply-To: pgilliam@us.ibm.com To: gdb@sources.redhat.com Subject: Re: Can't build on PowerPC-64 Date: Thu, 07 Jul 2005 20:38:00 -0000 User-Agent: KMail/1.6.2 Cc: Daniel Jacobowitz References: <200507061503.26454.pgilliam@us.ibm.com> <200507061718.58371.pgilliam@us.ibm.com> <20050707002053.GA14748@nevyn.them.org> In-Reply-To: <20050707002053.GA14748@nevyn.them.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200507071354.28874.pgilliam@us.ibm.com> X-SW-Source: 2005-07/txt/msg00073.txt.bz2 On Wednesday 06 July 2005 17:20, Daniel Jacobowitz wrote: > > Then I did this: > > gdb-ppc64-testing@dufur:~/adhoc-testing> find . -name vi.po > > ./src/opcodes/po/vi.po > > There should be one in src/bfd/po/vi.po. > > > gdb-ppc64-testing@dufur:~/adhoc-testing/src> cvs update > > cvs update: warning: failed to open /home/gdb-ppc64-testing/.cvspass for reading: No such file or directory > > What cvsroot do the snapshots use? Is it the wrong one? Cuz, you > didn't get vi.po, but I did... > > So I did this in the scr directory from the snapshot: cat CVS/Root and got: :pserver:anoncvs@sources.redhat.com:/cvs/src Then I did this in another directory: cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/src co gdb and got the normal ton of messages. Then I did this: find src -name vi.po and got: src/bfd/po/vi.po src/opcodes/po/vi.po So that particular snapshot (gdb-weekly-CVS-6.3.50.20050705.tar.bz2) is messed up, for whatever reason, and doesn't contain 'src/bfd/po/vi.po'. Now the strange part: 'cvs update' does not pick up the 'new' file. But if I edit CVS/Entries and add a fake line for the file, then do a cvs update, remove the file, and do another cvs update, and presto! I have the file. So I'm changing my automation to just use 'cvs checkout' instead of an 'ftp' of a snapshot and a 'cvs update'. -=# Paul #=-