public inbox for
help / color / mirror / Atom feed
Subject: insight/134: Problem at Installation
Date: Fri, 22 Mar 2002 11:23:00 -0000	[thread overview]
Message-ID: <> (raw)

>Number:         134
>Category:       insight
>Synopsis:       Problem at Installation
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Mar 22 11:23:01 PST 2002
>Release:        5.1.1
Win2K, Cygwin
My current version of cygwin has insight 5.0 with.  I wanted to upgrade it to 5.1.1 So --

Downloaded the Insight source to /usr/src/

On doing ./configure I get the following:
Administrator@SLOWSWARM /usr/src/insight-5.1
$ ./configure
Configuring for a i686-pc-cygwin host.
Created "Makefile" in /usr/src/insight-5.1 using "mh-frag"
/usr/lib/gcc-lib/i686-pc-cygwin/2.95.3-5/../../../../i686-pc-cygwin/bin/ld: cann
ot find -luser32
collect2: ld returned 1 exit status
*** The command 'gcc -o conftest -g -O2   conftest.c' failed.
*** You must set the environment variable CC to a working compiler.

I know the conftest.c does not exist.  My cygwin installationis complete as far as I know (selected installation of all components when running setup)

While I can live without upgrading the insight - I wish to also install the source navigator, but the exact same error message is generated when doing ./configure
Install cygwin (using the setup.exe from above).  Use for download site.  Download only then run setup.exe to install.

Download insight-5.1.1.tar.gz (or insight-5.1.tar.gz) from

expand in /usr/src and do ./configure
you tell me?

             reply	other threads:[~2002-03-22 19:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-22 11:23 Kumar.Mehta [this message]
2002-03-22 11:56 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:

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