public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Olivier Lefevre" <Olivier.Lefevre@biocrates.at>
To: <cygwin@cygwin.com>,<jason@tishler.net>
Subject: Re: Antw: Re: Cygwin python 2.3 oddity
Date: Thu, 11 Sep 2003 15:55:00 -0000	[thread overview]
Message-ID: <sf60b722.071@t-c-c.at> (raw)

> Why is the above "/c/cygwin/startup.py" and not "/startup.py" 
> as you previously indicated?

That's the same directory. I just made a typo the 1st time.

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

Now if only cygwin had an equivalent of Solaris truss; it might give us
a clue.

-- O.L.


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

             reply	other threads:[~2003-09-11 15:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-11 15:55 Olivier Lefevre [this message]
2003-09-11 17:28 ` Cliff Hones
  -- strict thread matches above, loose matches on Subject: below --
2003-09-11 21:55 Olivier Lefevre
2003-09-11 21:58 ` Antw: Re: cygwin " Christopher Faylor
2003-09-12 14:49   ` Jason Tishler
     [not found] <sf60b722.072@t-c-c.at>
2003-09-11 18:35 ` Antw: Re: Cygwin " Jason Tishler
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=sf60b722.071@t-c-c.at \
    --to=olivier.lefevre@biocrates.at \
    --cc=cygwin@cygwin.com \
    --cc=jason@tishler.net \
    /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).