Re: Can't build on PowerPC-64

[Paul Gilliam <pgilliam at us dot ibm dot com>]

On Wednesday 06 July 2005 17:20, Daniel Jacobowitz wrote:
<snip>
> > 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 #=-