From: L A Walsh <cygwin@tlinx.org>
To: cygwin@cygwin.com
Subject: Re: cygwin1.dll: uname_x not found
Date: Tue, 08 Sep 2020 11:28:17 -0700 [thread overview]
Message-ID: <5F57CD41.5040005@tlinx.org> (raw)
In-Reply-To: <20200908071849.GL4127@calimero.vinschen.de>
On 9/8/2020 12:18 AM, Corinna Vinschen wrote:
> On Sep 7 14:34, L A Walsh wrote:
>>> I uploaded new snapshots for testing to https://cygwin.com/snapshots/
>>>
>>> Please give them a try.
>> ---
>> Got:
>>
>> "The procedure entry point uname_x could not be located in the dynamic
>> link library cygwin1.dll"
>
> uname_x is exported just fine. You're doing something wrong.
>
> Corinna
---
I stopped all cygwin processes. Using cmd.exe, I renamed cygwin1.dll
to cygwin1.dll-. I 'copy'd the new dll in place and tried to run something.
What step did I miss?
Sorry, I know whatever I missed is obvious to you -- it always is obvious
to someone who knows the answer, but to those that don't know the answer,
it isn't at all obvious.
I have used test libraries before the same way and had them work. So I
don't know what I missed.
next prev parent reply other threads:[~2020-09-08 18:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 5:34 Weird behavior in 'grep'ing for string in /proc/registry L A Walsh
2020-09-07 7:05 ` Brian Inglis
2020-09-07 7:53 ` Thomas Wolff
2020-09-07 19:15 ` Brian Inglis
2020-09-07 20:51 ` Corinna Vinschen
2020-09-07 21:34 ` cygwin1.dll: uname_x not found L A Walsh
2020-09-08 7:18 ` Corinna Vinschen
2020-09-08 18:28 ` L A Walsh [this message]
2020-09-08 18:47 ` Thomas Wolff
2020-09-08 19:21 ` Corinna Vinschen
2020-09-08 19:21 ` Corinna Vinschen
2020-09-08 19:25 ` Corinna Vinschen
2020-09-07 14:02 ` Bug in 'grep'ing for string in /proc/registry L A Walsh
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=5F57CD41.5040005@tlinx.org \
--to=cygwin@tlinx.org \
--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).