From: "PAULUS, Raimund, TI-ABN" <Raimund.Paulus@dillinger.biz>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: RPC clnt_create() adress already in use
Date: Fri, 02 Mar 2018 10:39:00 -0000 [thread overview]
Message-ID: <59D90AF8D70E9740907BACDE2BCB520836F4021A@RESW102.resdom01.local> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1888 bytes --]
High Mark,
i did it already. Building cygwin1.dll in Cygwin 2.5.1 is ok, but using it delivers the message:
"The procedure entry point CancelSynchronousIo could not be located in the dynamic link library KERNEL32.dll".
It seems, i have to continue in using the old Cygwin 1.5.8 release for my Win XP SP3 boxes.
Raimund
-----Ursprüngliche Nachricht-----
Von: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] Im Auftrag von Mark Geisert
Gesendet: Mittwoch, 28. Februar 2018 07:00
An: cygwin@cygwin.com
Betreff: Re: RPC clnt_create() adress already in use
Corinna Vinschen wrote:
> On Feb 27 09:54, PAULUS, Raimund, TI-ABN wrote:
>> High Corinna,
>>
>> is it possible to get the patched cygwin1.dll for Cygwin 2.5.1? I have to support several older Win XP SP3 boxes.
>
> Sorry, we only support the current Cygwin build and keep the next
> older version as fallback. It's just not feasible to support version
> branches like the Linux kernel does, given the low number of active
> participants in this project.
>
> Nothing keeps you from building your own, though. The patches should
> apply mostly clean.
>
>
> Corinna
...And there's a FAQ that tells how to build the Cygwin DLL. Provided you have installed all the necessary tools listed there, it is straightforward to do.
https://cygwin.com/faq.html#faq.programming.building-cygwin
Something to consider,
..mark
--
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
\0ТÒÐÐ¥\a&ö&ÆVÒ\a&W\x06÷'G3¢\x02\x02\x02\x02\x02\x02\x06GG\x03¢òö7wvâæ6öÒ÷\a&ö&ÆV×2æFÖÀФd\x15\x13¢\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x06GG\x03¢òö7wvâæ6öÒöf\x17\x12ðФFö7VÖVçF\x17Föã¢\x02\x02\x02\x02\x02\x02\x02\x02\x06GG\x03¢òö7wvâæ6öÒöFö72æFÖÀÐ¥Vç7V'67&&R\x06æfó¢\x02\x02\x02\x02\x02\x06GG\x03¢òö7wvâæ6öÒöÖÂò7Vç7V'67&&R×6×\x06ÆPÐ Ð
next reply other threads:[~2018-03-02 10:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 10:39 PAULUS, Raimund, TI-ABN [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-08 11:44 PAULUS, Raimund, TI-ABN
2018-03-08 15:24 ` Corinna Vinschen
2018-03-08 23:00 ` Mark Geisert
2018-02-27 9:54 PAULUS, Raimund, TI-ABN
2018-02-27 10:37 ` Corinna Vinschen
2018-02-28 6:00 ` Mark Geisert
2018-02-06 11:29 PAULUS, Raimund, TI-ABN
2018-02-06 14:20 ` Corinna Vinschen
2018-02-07 6:54 ` Mark Geisert
2018-02-05 14:58 PAULUS, Raimund, TI-ABN
2018-02-05 8:19 PAULUS, Raimund, TI-ABN
2018-02-05 10:29 ` Mark Geisert
2018-02-05 11:26 ` Corinna Vinschen
2018-02-05 13:34 ` Corinna Vinschen
2018-02-05 14:06 ` Corinna Vinschen
2018-02-05 20:15 ` Corinna Vinschen
2018-02-02 12:58 PAULUS, Raimund, TI-ABN
2018-01-30 10:07 PAULUS, Raimund, TI-ABN
2018-01-31 8:15 ` Mark Geisert
2018-01-31 9:11 ` Corinna Vinschen
2018-01-31 9:35 ` Mark Geisert
2018-02-02 8:11 ` Mark Geisert
2018-01-30 7:01 PAULUS, Raimund, TI-ABN
2018-01-30 9:05 ` Mark Geisert
2017-12-19 16:13 PAULUS, Raimund, TI-ABN
2017-12-28 0:03 ` Mark Geisert
2017-09-29 9:52 PAULUS, Raimund, TI-ABN
2017-09-29 17:36 ` Mark Geisert
2017-09-27 12:51 PAULUS, Raimund, TI-ABN
2017-09-25 6:44 PAULUS, Raimund, TI-ABN
2017-09-27 9:50 ` Mark Geisert
2017-09-22 7:22 PAULUS, Raimund, TI-ABN
2017-09-24 9:49 ` Mark Geisert
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=59D90AF8D70E9740907BACDE2BCB520836F4021A@RESW102.resdom01.local \
--to=raimund.paulus@dillinger.biz \
--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).