Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Fri, 26 Mar 2004 10:12:05 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: popups upon library errors.
Message-ID: <20040326091205.GF17229@cygbert.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20040326033255 DOT GA16421 AT mdssdev05 DOT comp DOT pge DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040326033255.GA16421@mdssdev05.comp.pge.com>
User-Agent: Mutt/1.4.2i

On Mar 25 19:32, Edward S. Peschko wrote:
> After trying to compile cygwin from scratch, I've come to the conclusion that 
> opening up popup windows that require human interaction for system events is 
> well-nigh intolerable, and I'm hoping that something can be done to fix it.
> 
> Figure - I'm installing gettext, and configure is doing a bunch of checks 
> on my system.  It tries to find libICE, which is not installed, and isn't 
> even a fatal error in configuring gettext.
> 
> So - instead of going on to the next statement silently, I get a button 
> that I need to press in order to continue telling me of my 'error'. And hence
> stopping the configure process in its middle.

Off the top of my head I would say, that's a problem in your environment.
When the configury tests for existing libraries, it typically does that
by trying to build a test application which uses a function from that
lib.  A library might consist of up to three files, a static lib, an
import library for dynamic linking, and a DLL.  By default, ld tries to
link against the import library, so that the resulting application would
use the DLL when started.

On your system, the DLL is missing (or missing in $PATH, that's basically
the same) but for some reason the import library exists.  Linking the test
application therefore succeeds, but the resulting application can't run,
obviously.

So, to rectify this problem, you should remove the import library from
your system.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/