From: Andrey Repin <anrdaemon@yandex.ru>
To: Fran Litterio <flitterio@gmail.com>, cygwin@cygwin.com
Subject: Re: bash shell gets aborts under latest Windows 10 updates as of 4/2/17
Date: Fri, 05 May 2017 12:35:00 -0000 [thread overview]
Message-ID: <1476398630.20170505153144@yandex.ru> (raw)
In-Reply-To: <oehqu6$rp0$1@blaine.gmane.org>
Greetings, Fran Litterio!
> On 5/5/2017 7:30 AM, Andrey Repin wrote:
>>> You can rebase all the DLLs as follows:
>>
>> That's not how to do it.
>>
>> 1. Run
>>
>> rebase-trigger full
>>
>> 2. Shutdown all Cygwin processes.
>> 3. Run setup utility to the end.
> Thanks, Andrey. I have seen those instructions, but the rebaseall
> command itself says this when run in Bash:
> $ rebaseall
> rebaseall: only ash or dash processes are allowed during rebasing
> Exit all Cygwin processes and stop all Cygwin services.
> Execute ash (or dash) from Start/Run... or a cmd or command window.
> Execute '/bin/rebaseall' from ash (or dash).
> Is there evidence that the instructions displayed by rebaseall are
> incorrect? Is it possible that the setup utility simply runs rebaseall?
No, documentation of the utility is correct, but process you described is
obsolete. rebaseall was integrated into setup for a long time now.
--
With best regards,
Andrey Repin
Friday, May 5, 2017 15:28:48
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:[~2017-05-05 12:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <961799291.3143426.1491159192981.ref@mail.yahoo.com>
2017-04-02 18:53 ` gavin bowlby via cygwin
2017-04-02 20:20 ` gavin bowlby via cygwin
2017-05-04 16:52 ` Fran Litterio
2017-05-05 11:35 ` Andrey Repin
2017-05-05 12:24 ` Fran Litterio
2017-05-05 12:35 ` 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=1476398630.20170505153144@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=flitterio@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).