X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-2.6 required=5.0	tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_YG
X-Spam-Check-By: sourceware.org
Date: Sat, 5 Nov 2011 10:51:39 +0100
From: David Sastre <d.sastre.medina@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Problem with execution of binary file
Message-ID: <20111105095139.GA6441@jethro.local.lan>
References: <1320322806.5480.161.camel@kare-desktop> <4EB30E21.3090707@cs.umass.edu> <1320396611.5480.196.camel@kare-desktop> <4EB3C378.6060308@cs.umass.edu> <1320409986.5480.219.camel@kare-desktop> <loom.20111104T184732-309@post.gmane.org> <4EB42810.1000902@cs.umass.edu> <loom.20111104T191643-892@post.gmane.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="UlVJffcvxoiEqYs2"
Content-Disposition: inline
In-Reply-To: <loom.20111104T191643-892@post.gmane.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

--UlVJffcvxoiEqYs2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Nov 04, 2011 at 06:20:50PM +0000, Mark Geisert wrote:
> Eliot Moss writes:
> > I would add that having more than one cygwin installation
> > on the same system can be tricky, since you need to insure
> > that each program gets the right dlls, etc.
>=20
> Sheesh, it's so tricky that I assumed the OP meant he had separate VMs fo=
r his
> two Cygwin installations.  If they really are installed on one machine, a=
s the
> OP said, one 'cygcheck -svr' is enough.  I don't think the cygcheck has e=
ver
> been posted in this thread but is the main requirement asked on
> <http://cygwin.com/problems.html> when reporting problems.

Also note that the OP is using a home-brewed bash (might be
meaningful):

   22  111648 [main] bash 536 normalize_posix_path:
src /usr/local/bin/bash
   23  111671 [main] bash 536 normalize_posix_path: /usr/local/bin/bash
=3D normalize_posix_path (/usr/local/bin/bash)
   23  111694 [main] bash 536 mount_info::conv_to_win32_path:
conv_to_win32_path (/usr/local/bin/bash)
   22  111716 [main] bash 536 set_flags: flags: binary (0x2)
   24  111740 [main] bash 536 mount_info::conv_to_win32_path:
src_path /usr/local/bin/bash, dst C:\cygwin\usr\local\bin\bash, flags
0x3000A, rc 0

--=20
Huella de clave primaria: AD8F BDC0 5A2C FD5F A179  60E7 F79B AB04 5299 EC56

--UlVJffcvxoiEqYs2
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iF4EAREIAAYFAk61BysACgkQ95urBFKZ7FazogD/fg7v+9DJbDic4/3itfzRalVV
YJkicTLWvnZxXMYh1wwA/2/Y8fon8F42eOzxs8nVIo2IJFWM6Ytd/dZD2NzpUXov
=hGTc
-----END PGP SIGNATURE-----

--UlVJffcvxoiEqYs2--
