From: Mike O'Brien <jmobr7@gmail.com>
To: Marco Atzeri <marco.atzeri@gmail.com>, cygwin@cygwin.com
Subject: Re: Need upgrade/update advice/procedures: Cygwin32 to Cygwin64
Date: Sat, 15 Aug 2020 07:49:51 -0400 [thread overview]
Message-ID: <6dd3cff3-b7ac-4fbc-aa8e-954d5b7e3bf6@gmail.com> (raw)
In-Reply-To: <000ed0fd-325f-c3d7-fc52-24e76f91d276@gmail.com>
On 8/13/2020 3:10 PM, Marco Atzeri via Cygwin wrote:
> On 13.08.2020 20:25, Mike O'Brien via Cygwin wrote:
>> My first and only post —
>>
>> I would like to upgrade/update/switch from Cygwin32 to Cygwin64 (on
>> Win 7x64, sp1) and I'm not so sure what all the likely pitfalls may
>> be. Would appreciate any pertinent advice, informational links, etc.
>> that experienced users may wish to share. I've searched around and
>> pieced together a few insights, but I would be remiss not to ask here...
>>
>> TIA.
>>
>> Mike O'B.
>>
>
> duplicate installation with the attached script
>
> ./cyg-reinstall.sh -A
> sed -e "s/setup-x86/setup-x86_64/" cyg-reinstall-x86.bat >
> cyg-reinstall-x86_64.bat
>
> run the "cyg-reinstall-x86_64.bat" script in the same directory of
> "setup-x86_64.exe"
>
> after you can use your 32bit to copy the /home/<your_user>
> and all the content of "/etc" that you have customized.
>
> Regards
> Marco
>
> --
> Problem reports:https://cygwin.com/problems.html
> FAQ:https://cygwin.com/faq/
> Documentation:https://cygwin.com/docs.html
> Unsubscribe info:https://cygwin.com/ml/#unsubscribe-simple
All done and looking good!
That wasn't painful at all — much to my surprise . . .
Seriously though, thank you, Marco.
Mike O'B.
--
Mater mea, et are Hibernica Pater, et Ego Hibernica quoque!
next prev parent reply other threads:[~2020-08-15 11:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 18:25 Mike O'Brien
2020-08-13 19:10 ` Marco Atzeri
2020-08-15 11:49 ` Mike O'Brien [this message]
2020-08-15 13:31 ` Marco Atzeri
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=6dd3cff3-b7ac-4fbc-aa8e-954d5b7e3bf6@gmail.com \
--to=jmobr7@gmail.com \
--cc=cygwin@cygwin.com \
--cc=marco.atzeri@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).