public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: curl (7.27.0-1), even curl --version, does not work
Date: Tue, 04 Sep 2012 13:59:00 -0000	[thread overview]
Message-ID: <5046092E.9020001@cygwin.com> (raw)
In-Reply-To: <20120904135000.GA876@mail.nt1.in>

On 9/4/2012 9:50 AM, Regid Ichira wrote:
> Please cc your replies to the address this message is sent from.
> I am Regid, using another address.
> Continuing http://cygwin.com/ml/cygwin/2012-09/msg00020.html
>
> On Mon, 3 Sep 2012 12:54:45 +0200, Csaba Raduly wrote:
>
>> On Mon, Sep 3, 2012 at 11:56 AM, Regid Ichira  wrote:
>>> In reference to http://cygwin.com/ml/cygwin/2012-09/msg00015.html
>>> On Sun, 02 Sep 2012 16:36:27 -0500, Yaakov wrote
>>>
>>>> On Sun, 2012-09-02 at 13:50 -0700, Regid Ichira wrote:
>>>>> curl --version is supposed to only print version information.
>>>>> $ curl.exe --version
>>>>> $ printf "$?\n"
>>>>> 127
>>>>>
>>>>> I tried to strace it.
>>>>> $ strace.exe /usr/bin/curl.exe -V
>>>>>
>>>>> There was a popup window.  Its translated message was:
>>>>> curl.exe - system error
>>>>> {no entry point found} could not locate the entry point memrchr of
>>>>> the process in the dynamic linked library cygwin1.dll
>>>>
>>>> Then you don't have the latest version (1.7.16-1) of the 'cygwin'
>>>> package.
>>>
>>>    I do have it:
>>> $ cygcheck -c cygwin
>>> Cygwin Package Information
>>> Package              Version        Status
>>> cygwin               1.7.16-1       OK
>>>

True but...

>      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

... you're not running it.  Apparently, you've installed the new package
while other Cygwin programs were running (like your services) so it
couldn't replace the in-use old version.  Do a reboot.

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

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

  parent reply	other threads:[~2012-09-04 13:59 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
2012-09-04 13:59 ` marco atzeri
2012-09-04 13:59 ` Larry Hall (Cygwin) [this message]
  -- 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=5046092E.9020001@cygwin.com \
    --to=reply-to-list-only-lh@cygwin.com \
    --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).