From: Tilman Hausherr <tilman@snafu.de>
To: cygwin@cygwin.com
Subject: Re: Postinstall script errors
Date: Thu, 12 Aug 2010 19:50:58 +0200
Message-ID: <6pc866h187jhjjjsftioucjdd4t5uckhrc@4ax.com>
References: <AANLkTinNXnksnBKU7EKC4mFsqR9P5uAFsgTn0WyJ1Z=j@mail.gmail.com> <20100812095930.GX14202@calimero.vinschen.de>
In-Reply-To: <20100812095930.GX14202@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Thu, 12 Aug 2010 11:59:30 +0200, Corinna Vinschen wrote:

>That's probably a fault in the postinstall scripts.  It would be nice if
>you could provide more details about what fails exactly in the script,
>or better, what in the script has a non-0 exit code.  That would help us
>lazy maintainers to fix the scripts faster.
>
>Keep in mind that the dialog providing info about failing postinstall
>scripts is very new.  I'm quite sure that we have a couple of scripts
>which return with a non-0 exit code but the maintainers just don't know
>it yet, and I don't take myself out of the picture.

I'm not sure if these faulty postinstall scripts are really THAT
important, I got zero reaction on a bug report with details
http://sourceware.org/ml/cygwin/2010-08/msg00158.html

and I found out in the meantime that it was already reported in january
and was already a "known error" at that time.
http://old.nabble.com/gcc-command-not-found-td27393452.html#a27395128


Tilman


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