public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Programs become a no-op
Date: Thu, 03 May 2018 05:48:00 -0000	[thread overview]
Message-ID: <62215dc1-9209-666b-90f6-2c110cb71c94@SystematicSw.ab.ca> (raw)
In-Reply-To: <b80a51a1-fa55-77c6-ae76-d14bb240f439@acm.org>

On 2018-05-02 17:52, David Rothenberger wrote:
> Kaz Kylheku wrote:
>> On 2018-05-02 14:15, David Rothenberger wrote:
>>> On 5/2/2018 1:13 PM, Boylan, Ross wrote:
>>>> I've tried
>>>> ssh -V
>>>> ssh --help
>>>> ssh -v somene@somewhere
>>>> and in all cases nothing happens except that I get a new command 
>>>> prompt. They used to work fine.
>>> This is usually due to a missing dependency. You can try "echo $?" after
>>> one of the failing commands. If it is 127, that's probably the issue. I
>>> usually track down the missing dependency by running the program under
>>> strace (strace ssh --help). It should pop-up a dialog window with the
>>> missing dependency library.
>> What if it is 127 and the dialog says "The procedure entry point 
>> __locale_ctype_ptr could not be located in the dynamic link library
>> cygwin1.dll"?
>> That looks like an outdated cygwin1.dll w.r.t. that program (in this case 
>> gdb).
>> But why doesn't setup.exe ensure that cygwin1.dll is up-to-date for other 
>> things it installs?
> This can happen if you have Cygwin processes running when you run setup and 
> you ignore warnings. If I were you, I would first try a reboot. If that 
> doesn't work, I would ensure that all Cygwin processes and services are 
> stopped and then use setup to reinstall all your packages. If *that* doesn't 
> work, I would follow the instructions at http://cygwin.com/problems.html to 
> provide additional information for troubleshooting.
To check for incomplete setup due to interference, see if the following shows
anything amiss:

  $ /bin/ls -d -- /etc/postinstall/[!0z][!pqrst][!_]*.*sh    \
  >               /*bin/*.new /usr/*bin/*.new 2> /dev/null | \
  > /bin/egrep -vx '^/etc/postinstall/([0z][pqrst]_.*\..*sh|.*\..*sh\.done)$'

I run this in my Cygwin profile with suitable wrapping to let me know if setup
install or postinstall had issues, assuming Cygwin and coreutils are usable.

You can fix these issues outside Cygwin by renaming any .../*bin/*.new files
without the .new suffix, after renaming the original files to .old, when they
are not open or being used; then running any /etc/postinstall/*.*sh scripts,
whose names don't begin [0z]p_, under the required dash or bash shell, and
rename with added suffix .done if the shell script completes successfully.
This could be automated in a .cmd script using only cmd facilities and Windows
utilities with some effort: it's getting a bit easier on Windows (Powershell is
still mostly not standard/considered dangerous on corporate users' desktops),
but still nowhere nearly as easy as with bash/dash/sh on Cygwin.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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

  reply	other threads:[~2018-05-03  5:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-02 23:44 Kaz Kylheku
2018-05-02 23:55 ` David Rothenberger
2018-05-03  5:48   ` Brian Inglis [this message]
     [not found] <BY2PR05MB19571396AED3AB6AD820D4BA87800@BY2PR05MB1957.namprd05.prod.outlook.com>
2018-05-02 20:13 ` Boylan, Ross
2018-05-02 21:14   ` Marco Atzeri
2018-05-02 21:15   ` David Rothenberger
2018-05-03 13:35   ` Brian Inglis

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=62215dc1-9209-666b-90f6-2c110cb71c94@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@cygwin.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).