Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <000901c2e3ee$b7991620$78d96f83@pomello> From: "Max Bowsher" To: References: Subject: Re: Exception: STATUS_PRIVILEGED_INSTRUCTION occurs before main is executed. Date: Thu, 6 Mar 2003 14:43:13 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 > On Thu, 6 Mar 2003, Bruce Adams [TEPG Sunbury] wrote: >> I think it would be a great idea if the post setup phase did some >> basic configure style checking (assuming it doesn't already). >> i.e. >> Checking if the compiler gcc works.... No >> >> It would have saved me a couple of months of heartache. >> I seems very strange that nobody else spotted it though. >> How exactly could an installation become so corrupt that nothing >> short of >> a complete download (from a different mirror site) fixes it without >> the underlying package being in error? Somehow, it managed it, since there are lots of us who haven't done a clean install for ages. Igor Pechtchanski wrote: > I'm reasonably sure that if you create such a post-install script, it > will be at least thoughfully considered by the gcc maintainer... Well, I'm not the gcc maintainer, but I'd be surprised if such a script was accepted. Here's why: 1) There is no (good) way for a postinstall script to talk to the user. 2) If the package was broken immediately after installation, then wouldn't the maintainer have noticed before releasing it? Max. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/