From: "Norman Vine" <nhv@cape.com>
To: "'Michael Hudson'" <mwh@python.net>,
"'Jason Tishler'" <jason@tishler.net>
Cc: "'Cygwin'" <cygwin@sources.redhat.com>,
<david_abrahams@users.sourceforge.net>
Subject: RE: dll_list::load_after_fork() blues (was Re: [ python-Bugs-489709 ] Building Fails ...)
Date: Mon, 10 Dec 2001 10:46:00 -0000 [thread overview]
Message-ID: <008101c1819b$021aa860$a300a8c0@nhv> (raw)
In-Reply-To: <Pine.LNX.4.33.0112101516090.786-100000@starship.python.net>
Michael Hudson writes:
>
>On Mon, 10 Dec 2001, Jason Tishler wrote:
>
>> Unfortunately, when I run the complete Python regression test, I still
>> get the same three test failures as reported by Michael without rebasing:
>>
>> test_popen2
>> test_pty
>> test_socket
>>
>> When I run these tests individually (i.e., not part of the complete test
>> suite), then they pass. Hence, the rebasing appears not to completely
>> solve this problem.
>
>FWIW, and I don't know how much that is, all tests pass if I link _socket
>statically. Oh, and this is building without threads, it seems. I'll do
>a new build with threads and see if anything changes, but I doubt it.
GREAT IDEA !
I just rebuilt python 2.1.1 with threads and linking _socket statically
and all seems to work :-)
=== / usr / src / python-2.1.1 / Modules / Setup.local
# Edit this file for local setup changes
# socket line above, and possibly edit the SSL variable:
SSL=/usr
_socket socketmodule.c \
-DUSE_SSL -I$(SSL)/include -I$(SSL)/include/openssl \
-L$(SSL)/lib -lssl -lcrypto
Thanks Michael
Norman
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2001-12-10 16:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0112061015100.898-100000@starship.python.net>
2001-12-06 9:44 ` Jason Tishler
2001-12-06 10:12 ` Charles Wilson
2001-12-07 6:54 ` Michael Hudson
2001-12-07 7:03 ` David Abrahams
2001-12-07 7:32 ` Jason Tishler
2001-12-07 15:11 ` Robert Collins
2001-12-07 17:02 ` Charles Wilson
2001-12-07 17:29 ` Christopher Faylor
2001-12-12 5:14 ` rebase utility (was Re: dll_list::load_after_fork() blues ...) Jason Tishler
2001-12-12 5:45 ` Robert Collins
2001-12-12 6:04 ` Jason Tishler
2001-12-07 18:41 ` dll_list::load_after_fork() blues (was Re: [ python-Bugs-489709 ] Building Fails ...) Robert Collins
2001-12-07 18:19 ` Norman Vine
2001-12-07 18:44 ` Robert Collins
2001-12-10 4:46 ` Jason Tishler
2001-12-10 5:13 ` Robert Collins
2001-12-10 7:44 ` Jason Tishler
2001-12-16 0:12 ` Robert Collins
2001-12-10 7:23 ` Michael Hudson
2001-12-10 10:46 ` Norman Vine [this message]
2001-12-12 5:56 ` Jason Tishler
2001-12-18 13:12 ` Cygwin fork() rebase solution (was Re: dll_list::load_after_fork() blues ...) Jason Tishler
2001-12-18 14:07 ` Robert Collins
2001-12-18 19:56 ` cygwin " Christopher Faylor
2001-12-21 5:02 ` Jason Tishler
2001-12-22 17:08 ` Chris McDonough
2002-01-02 10:45 ` Jason Tishler
2001-12-19 22:46 ` Cygwin " Norman Vine
2001-12-16 0:31 ` dll_list::load_after_fork() blues (was Re: [ python-Bugs-489709 ] Building Fails ...) Robert Collins
2001-12-18 5:31 ` Jason Tishler
2001-12-18 6:35 ` Robert Collins
2001-12-07 6:04 ` Jason Tishler
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='008101c1819b$021aa860$a300a8c0@nhv' \
--to=nhv@cape.com \
--cc=cygwin@sources.redhat.com \
--cc=david_abrahams@users.sourceforge.net \
--cc=jason@tishler.net \
--cc=mwh@python.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).