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: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Thu, 6 Mar 2003 10:56:23 -0500 (EST)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Max Bowsher <maxb AT ukf DOT net>
cc: cygwin AT cygwin DOT com
Subject: Re: Exception: STATUS_PRIVILEGED_INSTRUCTION occurs before main is
  executed.
In-Reply-To: <000901c2e3ee$b7991620$78d96f83@pomello>
Message-ID: <Pine.GSO.4.44.0303061044090.21495-100000@slinky.cs.nyu.edu>
Importance: Normal
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 6 Mar 2003, Max Bowsher wrote:

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

Umm, I guess I should have expanded on my thought a bit more:  There are a
couple of standard fixes (chmod -R a+rx comes to mind) being suggested
over and over on the list.  I realize that this is a kludge, but I meant
for the script to detect that gcc is not working and attempt to fix it
using one of those methods.  On reflection, this may not have been such a
good suggestion after all...
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk!
  -- /usr/games/fortune


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