public inbox for
help / color / mirror / Atom feed
Subject: Re: insight/196: Problem with make gdb-5-1 : missing src/libtermcap
Date: Mon, 09 Dec 2002 16:52:00 -0000	[thread overview]
Message-ID: <> (raw)

Synopsis: Problem with make gdb-5-1 : missing src/libtermcap

Responsible-Changed-From-To: unassigned->kseitz
Responsible-Changed-By: kseitz
Responsible-Changed-When: Mon Dec  9 16:51:58 2002
    Mine. (Duh? Who else is there?)
State-Changed-From-To: open->feedback
State-Changed-By: kseitz
State-Changed-When: Mon Dec  9 16:51:58 2002
    Do you not have the src/libtermcap directory? Why use 5.1? IMO, you don't want to use this at all. You're best bet is to follow the directions off the website which will build you CVS head version of Insight using the 5.2 versions of tcl, tk, etc. This would probably be you're best route. Or just use 5.2. Although be advised, Win98 is known to be a bit flaky for cygwin (not really cygwin's fault -- Win98 is flaky!)
    In any case, please be aware that there is only one person who is really doing any work on insight (although I get one or two contributions from original developers occasionally). As such, no one should expect to get support from me. I run this bug database and the mailing list out of the stubbornness of my being. Insight is now essentially a one-man, unfunded, volunteer opensource project. Although almost all of the contributions come from addresses, NO ONE has worked on insight and been paid for it very well over a year.

             reply	other threads:[~2002-12-10  0:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-09 16:52 kseitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-09 15:53 michel.leconte

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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).