From: Jeremy Bennett <jeremy.bennett@embecosm.com>
To: gdb@sourceware.org
Subject: Problem (and solution) building from CVS
Date: Tue, 16 Sep 2008 13:25:00 -0000 [thread overview]
Message-ID: <1221571471.2827.324.camel@thomas> (raw)
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
Building failed, with a warning that Tcl definitions could not be found.
The problem is the gdb/gdbtk sub-directory. This directory does not
appear in the GIT download (even though that's mirrored from CVS).
Delete this directory from the CVS download and everything builds just
fine.
So it looks like some admin surgery may be needed to remove the
gdb/gdbtk directory from the CVS tree.
Jeremy
(thanks to Phil Muldoon for pointing me at the GIT alternative)
--
Tel: +44 (1202) 416955
Cell: +44 (7970) 676050
SkypeID: jeremybennett
Email: jeremy.bennett@embecosm.com
Web: www.embecosm.com
next reply other threads:[~2008-09-16 13:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 13:25 Jeremy Bennett [this message]
2008-09-16 13:31 ` Andreas Schwab
2008-09-16 13:48 ` Jeremy Bennett
2008-09-16 17:15 ` Tom Tromey
2008-09-16 15:02 ` Daniel Jacobowitz
2008-09-16 16:47 ` Jeremy Bennett
2008-09-16 17:21 ` Daniel Jacobowitz
2008-09-16 17:55 ` Jeremy Bennett
2008-09-16 18:27 ` Michael Snyder
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=1221571471.2827.324.camel@thomas \
--to=jeremy.bennett@embecosm.com \
--cc=gdb@sourceware.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