public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: Scott Bambrough <scottb@netwinder.org>
Cc: gdb@sources.redhat.com, Nick Clifton <nickc@cygnus.com>,
	Andrew Cagney <ac131313@cygnus.com>
Subject: Re: src/ltcf-c.sh
Date: Mon, 04 Sep 2000 18:11:00 -0000	[thread overview]
Message-ID: <20000904181111.A12745@lucon.org> (raw)
In-Reply-To: <00b201c016d5$2f8d2c00$LocalHost@netbackup>

On Mon, Sep 04, 2000 at 09:04:02PM -0400, Scott Bambrough wrote:
> 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.
> 

It works for me. I did

# cd gdb
# cvs -z 9 -d :pserver:anoncvs@anoncvs.cygnus.com:/cvs/src co gdb

to update my gdb checkout tree. src/ltcf-c.sh is there.


H.J.

  reply	other threads:[~2000-09-04 18:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-04 18:04 src/ltcf-c.sh Scott Bambrough
2000-09-04 18:11 ` H . J . Lu [this message]
2000-09-05 11:58 src/ltcf-c.sh Nick Clifton
2000-09-05 14:15 ` src/ltcf-c.sh Scott Bambrough
2000-09-05 14:19   ` src/ltcf-c.sh H . J . Lu
2000-09-05 14:41   ` src/ltcf-c.sh Daniel Berlin
2000-09-06  3:15     ` src/ltcf-c.sh Richard Earnshaw
2000-09-05 18:21 src/ltcf-c.sh Jason Molenda
2000-09-05 19:08 ` src/ltcf-c.sh Jason Molenda
2000-09-05 19:20   ` src/ltcf-c.sh Stan Shebs
2000-09-08  0:19   ` src/ltcf-c.sh Andrew Cagney
2000-09-08 10:04 src/ltcf-c.sh David Taylor

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=20000904181111.A12745@lucon.org \
    --to=hjl@lucon.org \
    --cc=ac131313@cygnus.com \
    --cc=gdb@sources.redhat.com \
    --cc=nickc@cygnus.com \
    --cc=scottb@netwinder.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).