public inbox for insight-prs@sourceware.org help / color / mirror / Atom feed
From: michel.leconte@cario.fr To: insight-gnats@sources.redhat.com Subject: insight/196: Problem with make gdb-5-1 : missing src/libtermcap Date: Mon, 09 Dec 2002 15:53:00 -0000 [thread overview] Message-ID: <20021209234730.6986.qmail@sources.redhat.com> (raw) >Number: 196 >Category: insight >Synopsis: Problem with make gdb-5-1 : missing src/libtermcap >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Dec 09 15:53:00 PST 2002 >Closed-Date: >Last-Modified: >Originator: michel.leconte@cario.fr >Release: 5-1.0 >Organization: >Environment: Windows98 - Cygwin 2.218.2.9 - PC Pentium III >Description: Hi, I would like to build a stable insight in a cygwin platform. For this, I follow the recommendations given in the html file located in : http://sources.redhat.com/insight/cygwin.htm After a "configure", I do a "make" and it fails after a long time. This failure seems to be relative to the missing of the directory : src/libtermcap The error's message is the following : Configuring in libtermcap /cygdrive/c/Programs/Cygwin/src/libtermcap/configure: Can't open /cygdrive/c/Programs/Cygwin/src/libtermcap/configure: No such file or directory make: *** [libtermcap/Makefile] Error 1 I need insight very quickly to end-up a project.. Thank you very much for any help >How-To-Repeat: after following the instructions in http://sources.redhat.com/insight/cygwin.htm do a "configure" and a "make".. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-12-09 23:53 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-09 15:53 michel.leconte [this message] 2002-12-09 16:52 kseitz
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=20021209234730.6986.qmail@sources.redhat.com \ --to=michel.leconte@cario.fr \ --cc=insight-gnats@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: linkBe 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).