Re: src/ltcf-c.sh

[Daniel Berlin <dan@cgsoftware.com>]

You'd have to use cvs update -dP, in the root dir, but this would then
procede to download other stuff you don't want that is in that cvs
repository.
In this case, your only option is to use checkout.

On Tue, 5 Sep 2000,
Scott Bambrough wrote:

> Actually on further testing, it gets me the file on checkout, but not on an
> update.
> 
> Scott
> 
> Nick Clifton wrote:
> > 
> > Hi Scott,
> > 
> > : The autobuild at netwinder.org fails with the following error:
> > :
> > : /home/build-rpm/BUILD/gdb/opcodes/../ltconfig:
> > : /home/build-rpm/BUILD/gdb/opcodes/../ltcf-c.sh: No such file or directory
> > : configure: error: libtool configure failed
> > : Configure in /home/build-rpm/BUILD/obj-gdb-20000904/opcodes failed, exiting.
> > : Bad exit status from /var/tmp/rpm-tmp.88907 (%build)
> > :
> > : The problem is a cvs checkout of gdb is not updating this file.  It isn't
> > : there so the build fails.  I had a look at the modules file, and it is
> > : included in the alias src-support, which is included in gdb-support which is
> > : used by the gdb module.  If I update my binutils tree, and my insight trees
> > : the file is not checked out, though I expect it to be.  If I check it out
> > : manually by cvs co ltcf-c.sh, it works.
> > :
> > : Any ideas?
> > 
> > Strange.  It seems to work for us.  Maybe this is a CVS bug ?
> > 
> > Cheers
> >         Nick
> 
>