Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Subject: RE: cygpath hangs from postinstall scripts when called like $(cygpath -S) but not otherwise From: Robert Collins To: alan.miles@ieee.org Cc: cygwin@cygwin.com, cygx In-Reply-To: References: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-GI89F+aV0nRw9hS1xv8H" Message-Id: <1065241514.18546.19.camel@localhost> Mime-Version: 1.0 Date: Sat, 04 Oct 2003 14:25:15 +1000 --=-GI89F+aV0nRw9hS1xv8H Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sat, 2003-10-04 at 14:19, Alan Miles wrote: > All, >=20 > I concur - I have a couple of private packages that I build, and then use= a > local copy of upset to create the setup.ini file. My packages are ** NOT = ** > XFree86 related, and I have the same type of $(cygpath -S) call in my > postinstall scripts. They also freeze up this latest setup.exe, the > 2.340.2.5 release of setup.exe everything worked properly. This is intruiging: these reports where already coming in before I pushed out the current release. (Which I did because I was finally tired of the 'setup hangs' reports due to the bad graph traversal code.) Rob --=20 GPG key available at: . --=-GI89F+aV0nRw9hS1xv8H Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQA/fkuqI5+kQ8LJcoIRAvjLAKCivlyJw3iqjU/VLvXTrNMVhu8jqwCcDwsi xfBQo9RO2EdY0FE3UbeQ+gI= =BcV/ -----END PGP SIGNATURE----- --=-GI89F+aV0nRw9hS1xv8H--