From: Jason Tishler <jason@tishler.net>
To: Olivier Lefevre <Olivier.Lefevre@biocrates.at>
Cc: cygwin@cygwin.com
Subject: Re: Antw: Re: Cygwin python 2.3 oddity
Date: Thu, 11 Sep 2003 18:35:00 -0000 [thread overview]
Message-ID: <20030911183903.GD888@tishler.net> (raw)
In-Reply-To: <sf60b722.072@t-c-c.at>
Olivier,
On Thu, Sep 11, 2003 at 05:55:37PM +0200, Olivier Lefevre wrote:
> > BTW, I just noticed that you are using Cygwin Python 2.3-1. Does
> > 2.3-2 work any better? The two packages are identical except for
> > 32- vs. 64-bit, but maybe this is the difference?
>
> I tried to install 2.3.2 and got "The procedure entry point __getreent
> could not be located in the dynamic link library cygwin1.dll", so I
> went back to 2.3.1. In any case, this is a standard PIV-based PC, no
> 64-bit here.
See the following:
http://cygwin.com/ml/cygwin-announce/2003-09/msg00001.html
http://cygwin.com/ml/cygwin-announce/2003-09/msg00041.html
Jason
--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next parent reply other threads:[~2003-09-11 18:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sf60b722.072@t-c-c.at>
2003-09-11 18:35 ` Jason Tishler [this message]
2003-09-11 21:55 Olivier Lefevre
2003-09-11 21:58 ` Antw: Re: cygwin " Christopher Faylor
2003-09-12 14:49 ` Jason Tishler
-- strict thread matches above, loose matches on Subject: below --
2003-09-11 15:55 Antw: Re: Cygwin " Olivier Lefevre
2003-09-11 17:28 ` Cliff Hones
2003-09-11 14:54 Olivier Lefevre
2003-09-11 15:39 ` Jason Tishler
[not found] <sf5fac54.018@t-c-c.at>
2003-09-11 14:16 ` Jason Tishler
2003-09-11 15:31 ` Antw: Re: cygwin " Christopher Faylor
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=20030911183903.GD888@tishler.net \
--to=jason@tishler.net \
--cc=Olivier.Lefevre@biocrates.at \
--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).