Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Subject: Re: Running setup twice on a new install From: Robert Collins To: Karl M Cc: cygwin AT cygwin DOT com In-Reply-To: References: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-lzSALuk9/fRWuH2iMHZ2" Message-Id: <1075587566.1163.46.camel@localhost> Mime-Version: 1.0 Date: Sun, 01 Feb 2004 09:19:26 +1100 X-IsSubscribed: yes --=-lzSALuk9/fRWuH2iMHZ2 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sun, 2004-02-01 at 04:34, Karl M wrote: > Hi All... >=20 > I did a new cygwin install last week and I again saw the following behavi= or:=20 > I ran setup twice (one > right after the other). In the first run everything seemed fine. On the= =20 > second run, setup told me I > needed >=20 > libbz2_1: Shared libraries for bzip2 (runtime) >=20 > so I let it install it. This was on a win-xp-pro box, but I have seen it = on=20 > 98,2k and xp. >=20 > My question is why is this not detected on the first pass? I don't know at this point. Possibly a bug in the loop breaking logic. We'd need to know what loops where printout out in setup.log.full for the first run. Rob --=20 GPG key available at: . --=-lzSALuk9/fRWuH2iMHZ2 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBAHCnuI5+kQ8LJcoIRAua2AJ4jBxAsxUEWFeg452VMBTI+rfRahwCfUS6a uOp9gRnWMN7hnsXMumkWNe0= =uTUx -----END PGP SIGNATURE----- --=-lzSALuk9/fRWuH2iMHZ2--