From: Andrey Repin <anrdaemon@freemail.ru>
To: Kenneth Wolcott <kennethwolcott@gmail.com>, cygwin@cygwin.com
Subject: Re: please update the supported Cygwin package list to be distinct for 32-bit, 64-bit or both; and help on how install both in a merged fashion
Date: Sat, 27 Jul 2013 05:28:00 -0000 [thread overview]
Message-ID: <772541565.20130727091340@mtu-net.ru> (raw)
In-Reply-To: <CADex0xxLK3LRfHcat8UYXDUoYxRu5OPzV0_+FXMKd7k_J4G+Vg@mail.gmail.com>
Greetings, Kenneth Wolcott!
> please update the supported Cygwin package list to be distinct for
> 32-bit, 64-bit or both; and help on how install both in a merged
> fashion
> I noticed cgf's "mirrored" cgwin installation for 64-bit and 32-bit
> Cygwin: very nice.
> Now, you guys might think I'm 100% nuts, but I download *everything*
> and install *everything* from Cygwin, although there is very little
> that I configure (I use the applications out-of-the-box). [for
> example, I never have configured an ssh server on Cygwin].
> So, not all of the Cygwin packages are 64-bit yet (looking forward to that day).
> So, what I would like to do is:
> 1. download all 64-bit packages;
> 2. download all 32-bit packages that aren't already represented in 64-bit form;
> 3. somehow install so that I have everything from both #1 and #2;
That's not how things are supposed to work. And all the necessary packages
will eventually be updated to 64-bit, or obsoleted/removed.
The very simple reason is that you can't load 64-bit DLL into 32-bit process
without much fiddling around.
> I could do the following:
> 1. Download all of the 64-bit Cygwin packages;
> 2. Download all of the 32-bit packages (inefficient, but the command
> line install is hard to program);
> 3. Delete all 32-bit packages that are represented in the 64-bit download;
> 4. modify the text file (?) installed_db?
> 5. Install from the download directory the 64-bit products;
> 6. install from the download directory the 32-bit products;
> Now, is there a better way to do this?
> Another thought that I had was that I would have two distinct Cygwin
> installations, one fully 64-bit and the other one would be fully
> 32-bit.
> I guess what I'd like to have is a hybrid of cgf's method and the
> combination of two distinct Cygwin installations, one 32-bit and the
> other 64-bit.
You can just use 32-bit installation, if 64-bit is missing anything you're
using daily. I see no issues.
--
WBR,
Andrey Repin (anrdaemon@freemail.ru) 27.07.2013, <09:10>
Sorry for my terrible english...
--
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
prev parent reply other threads:[~2013-07-27 5:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-27 3:32 Kenneth Wolcott
2013-07-27 5:20 ` marco atzeri
2013-07-27 5:24 ` Kenneth Wolcott
2013-07-27 6:20 ` LRN
2013-07-27 7:26 ` Andrey Repin
2013-07-27 10:30 ` LRN
2013-07-27 6:29 ` marco atzeri
2013-07-27 7:57 ` Warren Young
[not found] ` <51F9A3BE.4020907@tlinx.org>
2013-08-01 0:28 ` having 1 set of non-bin files w/separate {bin,lib}[32/64)? (was Re: please update the supported Cygwin package list ...) Warren Young
2013-08-03 11:33 ` Linda Walsh
2013-08-03 15:48 ` Earnie Boyd
2013-08-04 2:19 ` Linda Walsh
2013-08-04 3:54 ` Earnie Boyd
2013-08-04 4:56 ` Linda Walsh
2013-07-27 5:28 ` Andrey Repin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=772541565.20130727091340@mtu-net.ru \
--to=anrdaemon@freemail.ru \
--cc=cygwin@cygwin.com \
--cc=kennethwolcott@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).