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
X-Authentication-Warning:	mdssdev05.comp.pge.com: esp5 set sender to esp5 AT pge DOT com using -f
Date:	Thu, 25 Mar 2004 19:32:55 -0800
From:	"Edward S. Peschko" <esp5 AT pge DOT com>
To:	cygwin AT cygwin DOT com
Subject:	popups upon library errors.
Message-ID:	<20040326033255.GA16421@mdssdev05.comp.pge.com>
Mime-Version:	1.0
User-Agent:	Mutt/1.4.1i
X-IsSubscribed:	yes

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.

How am I supposed to automate anything with this behavior? I don't want a 
cron job silently failing and instead of sending out a window that someone 
needs to click - and hence delaying a page being sent - I want the window
to go away automatically and the page to be sent showing error.

Given that when I run processes in strace this behaviour seems to go away
suggests that this isn't something inherent in windows and is fixable.
So - is there a standard way to fix this?

Ed

--
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/

- Raw text -