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: Tue, 6 Apr 2004 12:08:19 -0700
From: "Edward S. Peschko" <esp5 AT pge DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: errors coming from building from scratch
Message-ID: <20040406190819.GB13267@mdssdev05.comp.pge.com>
References: <20040406020236 DOT GA11062 AT mdssdev05 DOT comp DOT pge DOT com> <4968407554 DOT 20040406121907 AT familiehaase DOT de> <20040406184304 DOT GA13267 AT mdssdev05 DOT comp DOT pge DOT com> <20040406185402 DOT GA20805 AT cygbert DOT vinschen DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040406185402.GA20805@cygbert.vinschen.de>
User-Agent: Mutt/1.4.1i
X-IsSubscribed: yes

On Tue, Apr 06, 2004 at 08:54:02PM +0200, Corinna Vinschen wrote:
> On Apr  6 11:43, Edward S. Peschko wrote:
> > I don't see why cygwin could internalize this behavior and provide a consistant way
> > of displaying linking errors via text rather than annoying popups..
> 
> Since it has nothing to do with Cygwin, perhaps?  When an application
> is linked against a DLL, the loader process is a Windows internal
> thingy.

but's that's the issue - rxvt *does* do this correctly. As does strace. When you get a 
'can't load X server' or other file error, it comes to the console not to a popup.

Why can't cygwin mimic the rxvt behaviour, so each client app (gcc for example) gets
it for free rather than needing to re-invent it?

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/