DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=w+w+jGWnmfdof4R4oLP6HwVk4KoGYwZuizqyFMn/3p6Ar1L4Pm1DK
	VMlwh0ANebHOU/Xm/3Jc0oLLEwN7Q5KpuQkLFat+MqW/HnmgvXaMxL5qdk6kVubm
	rJMdihQmR7HvWb37hgnzkZSGPLORZtNxN8WVrsxhw1HnJtAfd56nqk=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Sun, 15 Feb 2015 10:25:38 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: 1.7.35 Bash spawned by Perl has DOS-style argv0
Message-ID: <20150215092538.GE7225@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <CAGeuTF1Q9d1P2mmZrugLaN2_i1a+q2hQ++mDARdjymb2tT2aEg AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="Pd0ReVV5GZGQvF3a"
Content-Disposition: inline
In-Reply-To: <CAGeuTF1Q9d1P2mmZrugLaN2_i1a+q2hQ++mDARdjymb2tT2aEg@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)

--Pd0ReVV5GZGQvF3a
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Feb 14 14:23, John Warburton wrote:
> Hello,
>=20
> After upgrading my installation from about two months ago to 1.7.35, a
> Bash shell opened by Perl (as used in Gnu Autotools) now sees
> DOS-style paths in its $argv0 variable instead of Unix-style paths
> and, consequently, errors occur. Before I upgraded my installation,
> everything was fine.
>=20
> Here is a simple test case I have written.
> [...]
>    Filename 2: perlpath.pl
>=20
> use Cwd 'abs_path';
> print "My absolute path is: ";
> print abs_path($0);
> print "\n";
> print "Now to run Bash again, and view its argv...\n";
> system ("./pathtest_2.sh");
>=20
>    Filename 3: pathtest_2.sh
>=20
> argv0=3D${0##*/}
> echo "After execution from Perl, I have set argv0 to ${argv0} and 0 to ${=
0}"
> echo "This is Bash version ${BASH_VERSION}"

Thanks for the testcase!  The problem you're describing is the result of
a thinko when I revamped the PATH finding functionality in Cygwin a
couple of days ago.  I fixed that in CVS.  I will upload a new developer
snapshot for testing to https://cygwin.com/snapshots/ later today.

> Is anyone else experiencing this? Are there any ways to force Bash
> shells run from Cygwin Perl to see Unix style paths, especially when
> Perl itself reports a Unix style path?

You *did* notice that 1.7.35 is a *test* release, did you?

Fortunately you actually tested it before it was released :)

The actual official stable release is 1.7.34, and it's of course
not affected by this problem.


Thanks,
Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--Pd0ReVV5GZGQvF3a
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJU4GYSAAoJEPU2Bp2uRE+ggIQP/3WVBFEhtEk2tC5eAr4S6LJo
1H0X3LEycPf6JWePJeXUeadxJAeadj5vpoNs+PWtbfNJnITdXZ0J0YqArnV0qwrH
SFV+TdW5CMFj1YVEoS/So+arhS8loKZWDXI0BgltOdTxlZr2OuMXRiO72kkKvzU6
dWxgH3Hj1xVI6IS3V+pKc4nEc4r8ARsa0HbgYS0BlekhFt4Tb1cPZlFVPCJ5LadL
CPwXy3xFg9goSxDcg9ZUDxH5kevgwStJ3sVjiuO7UxVpzQyaAgbufFfH1yIm3lyy
Tf+DEKxaTfipc8fSDFo4tch+jn6djurg7FpBTOB4U0EAMneI+7xGbkQN/v0rIq9I
SgMtMy1VD5VU/VeH8+YQ7JJo0k0Dj77TnWS0pm1UguFo3l1kipH6RkGeIR+T4s+E
7LZ+YzxUgT36HqGEYJWnax1CothQPedKVk5+JfZvOV61nB7WsV8QDpLx1J1rNcII
ZpAEchWcPrldWJ015HmlKgRfUrihRvTM+VjA7xSmA/XVQhO3RnugL39U3hN5mZSz
aoK/4qRv3NTfod1jxnpjV7M+tEndcXxulRLQhT6J+KPyTu/PQtw+1SeJAbZvb92w
Lji4h0XffKPYTfgmnKWoCex1ZDfmgzs3w9vdoPgK8ei/hyDOVUGsAd30a8Wu+F4X
zYBIuURoTm6K5oLGUN1v
=DWTm
-----END PGP SIGNATURE-----

--Pd0ReVV5GZGQvF3a--