From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: Perl5 & kenji arisawa's perl question
Date: Mon, 6 Nov 2000 08:08:38 +0000 [thread overview]
Message-ID: <E13shKY-000OOh-0A@finch-post-10.mail.demon.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 29 bytes --]
So where is it available?
[-- Attachment #2: Type: message/rfc822, Size: 2572 bytes --]
From: Jonathan Sergent <sergent@csociety.purdue.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: Perl5 & kenji arisawa's perl question
Date: Mon, 06 Nov 2000 03:03:23 -0500
Message-ID: <200011060803.DAA12456@csociety.ecn.purdue.edu>
>
> I also thank Nigel. Please give me Python 1.6.
>
How's this:
$ ls -l python
--rwxr-xr-x M 3 sergent sergent 3193673 Nov 5 23:27 python
$ ./python
Python 2.0 (#3, Nov 5 2000, 23:27:32) [C] on plan91
Type "copyright", "credits" or "license" for more information.
>>>
Check out that executable size...
Usually Python uses dynamic linking to load most of the modules. If I get
up the courage, I will see if I can make GNU dld work (it does dynamic
module loading, supposedly portably, but I have not looked into it)
since Python already has support for it.
Out of the regression test suite, test_cmath, test_openpty, test_popen2,
and test_socket failed. The first two caused python to suicide; the
second two generated error messages. The test_socket error was a host
name resolution thing. Does gethostbyname in APE work? Does DNS work
with it? Seems like someone mentioned this a while back.
Building Python was not that hard; I spent maybe two hours.
It's probably not that useful without the dynamic module loading, which
most Python programs I have seen use to load C code. This would also
reduce the python executable size significantly...
--jss.
next reply other threads:[~2000-11-06 8:08 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-06 8:08 nigel [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-09 18:54 bwc
2000-11-09 17:44 anothy
2000-11-09 19:15 ` Boyd Roberts
2000-11-09 16:51 Dave Atkin
2000-11-09 21:52 ` Steve Kilbane
2000-11-09 22:00 ` Boyd Roberts
2000-11-09 16:10 erik quanstrom
2000-11-09 15:29 rog
2000-11-09 14:42 ` Boyd Roberts
2000-11-09 13:48 bwc
2000-11-08 18:39 Russ Cox
2000-11-08 22:34 ` Boyd Roberts
2000-11-08 22:59 ` andrey mirtchovski
2000-11-08 23:15 ` Boyd Roberts
2000-11-09 7:45 ` Steve Kilbane
2000-11-09 9:33 ` Greg Shubin
2000-11-08 18:35 David Gordon Hogan
2000-11-08 16:45 rog
2000-11-08 22:06 ` Boyd Roberts
2000-11-08 15:57 forsyth
2000-11-08 15:36 anothy
2000-11-08 13:56 rog
2000-11-08 13:11 ` Boyd Roberts
2000-11-07 23:30 anothy
2000-11-07 16:24 Re[2]: " steve.simon
2000-11-07 16:44 ` Boyd Roberts
2000-11-07 18:30 ` Douglas A. Gwyn
2000-11-07 18:58 ` Boyd Roberts
2000-11-08 9:23 ` George Michaelson
2000-11-08 12:38 ` Boyd Roberts
2000-11-08 18:13 ` Greg Shubin
2000-11-08 22:27 ` Boyd Roberts
2000-11-06 16:17 forsyth
2000-11-05 7:34 [9fans] " andrey mirtchovski
2000-11-05 9:31 ` [9fans] Re: Perl5 & " arisawa
2000-11-06 8:03 ` Jonathan Sergent
2000-11-06 15:45 ` Scott Schwartz
2000-11-06 15:51 ` Boyd Roberts
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=E13shKY-000OOh-0A@finch-post-10.mail.demon.net \
--to=nigel@9fs.org \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).