From: Fred Fish <fnf@public.ninemoons.com>
To: insight@sources.redhat.com
Cc: fnf@ninemoons.com
Subject: current version from CVS fails build
Date: Wed, 29 Jan 2003 19:33:00 -0000 [thread overview]
Message-ID: <200301291935.h0TJZNGp010305@fred.ninemoons.com> (raw)
For the last few days, the latest version from the CVS repository has been
failing to build for me. The error is:
make[2]: Entering directory `/links/build/sourceware/gdb/T-i686-pc-linux-gnu/tix/unix'
/bin/sh: line 1: cd: tk8.4: No such file or directory
This is coming from the following in tix/unix/Makefile:
# CYGNUS LOCAL: Just recur for most targets:
SUBDIR = tk8.4
all test:
@cd $(SUBDIR) && $(MAKE) $@
and there is no tk8.4 subdir.
-Fred
next reply other threads:[~2003-01-29 19:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 19:33 Fred Fish [this message]
2003-01-29 19:37 ` Christopher Faylor
2003-01-29 19:49 ` Fred Fish
2003-01-29 19:52 ` Keith Seitz
2003-01-29 20:09 ` Fred Fish
2003-01-29 20:41 ` Andrew Cagney
2003-01-29 20:45 ` Mo DeJong
2003-01-29 20:48 ` Keith Seitz
2003-01-29 20:57 ` Andrew Cagney
2003-01-29 21:00 ` Keith Seitz
2003-01-29 20:54 ` Christopher Faylor
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=200301291935.h0TJZNGp010305@fred.ninemoons.com \
--to=fnf@public.ninemoons.com \
--cc=fnf@ninemoons.com \
--cc=insight@sources.redhat.com \
/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).