public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Robert Cragie <rcc@jennic.com>
Cc: SID <sid@sources.redhat.com>
Subject: Re: FW: Can't get SID to build - tk error
Date: Thu, 06 Feb 2003 17:47:00 -0000	[thread overview]
Message-ID: <20030206124725.C21480@redhat.com> (raw)
In-Reply-To: <NMEDLDELHPEFHOMFIJBHAEDBCKAA.rcc@jennic.com>; from rcc@jennic.com on Thu, Feb 06, 2003 at 05:31:55PM -0000

[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]

Hi -


On Thu, Feb 06, 2003 at 05:31:55PM -0000, Robert Cragie wrote:
> [...]
> This is obviously residue from earlier checkouts of SID, as I notice it is
> present in an earlier source tree but, as you rightly say, it is not in the
> latest source tree. I did update my source tree using 'cvs -z9
> update -d -P', which I thought would have removed any directories no longer
> relevant. 

It would do that, only if irrelevant directores were identified
with an "cvs remove", to actually designate them as if deleted.
Because that source subtree (buggy as it is) is still used by
insight and snavigator, it can't be "cvs remove"d.  Your "cvs update -d -P"
dutifully pulled it (and everything else under src/) into your
working tree.


> However, I have done a clean checkout and will work from there. I
> have applied the [tcl 8.3->8.4] patch and have started a build -
> the results look promising so far.

I'm glad to hear.  I'll commit a variety of C++ and build cleanups
to src/sid in the coming days, including that patch.


- FChE

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2003-02-06 17:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-06 12:49 Robert Cragie
2003-02-06 15:56 ` Frank Ch. Eigler
2003-02-06 17:31   ` Robert Cragie
2003-02-06 17:47     ` Frank Ch. Eigler [this message]

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=20030206124725.C21480@redhat.com \
    --to=fche@redhat.com \
    --cc=rcc@jennic.com \
    --cc=sid@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).