Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Date:	Mon, 5 Sep 2005 23:52:47 -0400 (EDT)
From:	Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To:	cygwin AT cygwin DOT com
To:	Luke Kendall <luke DOT kendall AT cisra DOT canon DOT com DOT au>
cc:	cygwin AT cygwin DOT com
Subject:	Re: Odd transient error about __impure_ptr
In-Reply-To:	<20050906032541.553BB83C6F@pessard.research.canon.com.au>
Message-ID:	<Pine.GSO.4.63.0509052347120.504@slinky.cs.nyu.edu>
References:	<20050906032541 DOT 553BB83C6F AT pessard DOT research DOT canon DOT com DOT au>
MIME-Version:	1.0

On Tue, 6 Sep 2005, Luke Kendall wrote:

> On a freshly (re?)installed copy of Cygwin from September 2004, a weird
> thing happened that I thought I'd mention.  We use Michael Wardle's
> excellent shell.c program that queries the password file to find the
> user's default shell, to start that (instead of running bash --login),
> run from inside a .bat file with a shortcut on the desktop.
>
> I *think* I may have compiled this with a later version of Cygwin.
> Anyway, when we recently dusted off and installed the Sept '04 Cygwin,
> trying to run shell.exe lead to a failure, with the message that
> cygwin1.dll did not provide __impure_ptr.
>
> So I recompiled it from the freshly-installed stable release.
> It failed the same way.  Then I ran it from inside a Cygwin shell
> (inside rxvt), and it worked!  I then changed the .bat file for the
> shortcut back the way it had been, and it also worked!
>
> Does that make sense to anyone?  It's no big deal, just something weird
> that I thought someone more knowledgeable than I might understand.

Hard to say without a proper problem report[*], but it sounds like you
have another version of cygwin1.dll in the PATH.  Windows looks for
cygwin1.dll in the directory of the program before it looks at the PATH,
and the standard cygwin.bat runs bash from /bin, so it finds the new DLL.
If your shell.exe is in another directory, the older DLL in the PATH will
take precedence.
HTH,
	Igor
[*] <http://cygwin.com/problems.html>
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. /DA

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