X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.4 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <BANLkTi=-kRq+xMtJsFNcbQP5NkWS+FOL-A@mail.gmail.com>
References: <BANLkTikt4vmXrMm824W7qc+_Qwce+HfyLA AT mail DOT gmail DOT com>	<BANLkTin=Mh7kEfM04tCrbOJequJHomVyjg AT mail DOT gmail DOT com>	<BANLkTi=-kRq+xMtJsFNcbQP5NkWS+FOL-A AT mail DOT gmail DOT com>
Date: Sun, 26 Jun 2011 00:41:08 -0400
Message-ID: <BANLkTimcW-pZsMf79SibGJ3TRGuGgO6vsQ@mail.gmail.com>
Subject: Re: Creating package directory for Windows 7 64-bit from Windows XP Pro 32-bit
From: Andrew Hancock <andymhancock AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id p5Q4fXbc030793

On Wed, Jun 22, 2011 at 12:55 AM, Andrew Hancock <andymhancock AT gmail DOT com> wrote:
>
> I have a 32-bit XP Pro machine with an old cygwin installation (DLL
> version 1.5.25).  In the past, started Setup on a machine on which
> cygwin was already installed an created a package directory on CD with
> the same packages as the installation.  I can then install the same
> packages on another 32-bit XP Pro machine.  I was going to do the
> same, but with the target computer being a 64-bit Windows 7 Pro
> computer.  From my surfing, I don't expect the 64-bit to present a
> problem.  What about the fact that the source and destination
> computers are different OS's?  Can some of the downloaded files be
> specific an OS?

Well, it looks like it became a moot point.  I ran into the legendary
error "Can't open (null) for reading: No such file".  So I ended up
picking and choosing packages from the full buffet of packages again.
As it turned out, this was the better way.  Lots of stuff I don't use
anymore.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple