public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Thrall, Bryan" <bryan.thrall@flightsafety.com>
To: "Regid Ichira" <regid23@mail.nt1.in>,	<cygwin@cygwin.com>
Cc: "Thrall, Bryan" <bryan.thrall@flightsafety.com>
Subject: RE: curl (7.27.0-1), even curl --version, does not work
Date: Tue, 04 Sep 2012 13:58:00 -0000	[thread overview]
Message-ID: <786EBDA1AC46254B813E200779E7AD3602635684@srv1163ex1.flightsafety.com> (raw)
In-Reply-To: <20120904135000.GA876@mail.nt1.in>

FYI, please *attach* cygcheck output in the future so it doesn't clutter
up search results.

This:

Regid Ichira wrote on 2012-09-04: 
>>>   I do have it:
>>> $ cygcheck -c cygwin
>>> Cygwin Package Information
>>> Package              Version        Status
>>> cygwin               1.7.16-1       OK

Does not match this:

>  2779k 2012/04/25 C:\externalPrograms\cygwin\root\bin\cygwin1.dll -
os=4.0
> img=1.0 sys=4.0
>                   "cygwin1.dll" v0.0 ts=2012/4/25 8:41
>     Cygwin DLL version info:
>         DLL version: 1.7.14
>         DLL epoch: 19
>         DLL old termios: 5
>         DLL malloc env: 28
>         Cygwin conv: 181
>         API major: 0
>         API minor: 260
>         Shared data: 5
>         DLL identifier: cygwin1
>         Mount registry: 3
>         Cygwin registry name: Cygwin
>         Program options name: Program Options
>         Installations name: Installations
>         Cygdrive default prefix:
>         Build date:
>         Shared id: cygwin1S5

My guess is you had Cygwin processes running when you upgraded from
1.7.14 to 1.7.16 and did not reboot afterwards (there should be a
cygwin1.dll.new in your /bin directory). Or, as I understand happens
sometimes, the Windows replace-on-reboot feature failed.

The safest thing to do to fix the problem would be to close all Cygwin
processes and reinstall the Cygwin package.

If you want to get your hands dirty, you could close all Cygwin
processes and replace your existing cygwin1.dll with cygwin1.dll.new.

Hope this helps,
--
Bryan Thrall
Principal Software Engineer
FlightSafety International
bryan.thrall@flightsafety.com



--
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:[~2012-09-04 13:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-04 13:50 Regid Ichira
2012-09-04 13:58 ` Thrall, Bryan [this message]
2012-09-04 13:59 ` marco atzeri
2012-09-04 13:59 ` Larry Hall (Cygwin)
  -- strict thread matches above, loose matches on Subject: below --
2012-09-03  9:56 Regid Ichira
2012-09-03 10:55 ` Csaba Raduly
2012-09-02 20:50 Regid Ichira
2012-09-02 21:36 ` Yaakov (Cygwin/X)

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=786EBDA1AC46254B813E200779E7AD3602635684@srv1163ex1.flightsafety.com \
    --to=bryan.thrall@flightsafety.com \
    --cc=cygwin@cygwin.com \
    --cc=regid23@mail.nt1.in \
    /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).