From: "Federico G. Benavento" <benavento@gmail.com>
To: erik quanstrom <quanstro@quanstro.net>
Cc: 9fans@9fans.net
Subject: Re: [9fans] trying to populate arm tree
Date: Mon, 28 Jan 2013 12:53:37 -0300 [thread overview]
Message-ID: <4E58139C-6796-42C3-973B-76C6E00CFBD0@gmail.com> (raw)
In-Reply-To: <2f29a133caba1c87e7ad7d5999d74daf@brasstown.quanstro.net>
I just compiled it for arm with my changes… haven't tested it though.
lotte% file /arm/bin/python
/arm/bin/python: arm plan 9 executable
how does one get https without openssl, do you have to reimplement
tons of things?
On Jan 28, 2013, at 12:32 PM, erik quanstrom <quanstro@quanstro.net> wrote:
>> python needs a mkfile rework.
>
> i'm afraid it's more serious than that. python is out of date,
> only compiles for 386, there are file i/o problems, etc,
> it drags along openssh/openssl, and isn't pushed upstream.
>
> jeff is working on a addressing all these issues with the latest
> 2.x python. it will be put on sources when its ready.
>
> - erik
---
Federico G. Benavento
benavento@gmail.com
next prev parent reply other threads:[~2013-01-28 15:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 12:46 James Chapman
2013-01-28 14:32 ` Jens Staal
2013-01-28 14:53 ` Federico G. Benavento
2013-01-28 15:07 ` Federico G. Benavento
2013-01-28 15:38 ` James Chapman
2013-01-28 15:30 ` James Chapman
2013-01-28 16:47 ` Federico G. Benavento
2013-01-28 17:20 ` James Chapman
2013-01-28 17:40 ` Jeff Sickel
2013-01-28 18:21 ` erik quanstrom
2013-01-28 18:26 ` Federico G. Benavento
2013-01-28 20:10 ` erik quanstrom
2013-01-28 20:14 ` Federico G. Benavento
2013-01-29 22:07 ` Richard Miller
2013-01-29 22:02 ` Richard Miller
2013-01-28 15:32 ` erik quanstrom
2013-01-28 15:53 ` Federico G. Benavento [this message]
2013-01-28 16:25 ` Jacob Todd
2013-01-28 16:40 ` Matthew Veety
2013-01-28 16:40 ` Federico G. Benavento
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=4E58139C-6796-42C3-973B-76C6E00CFBD0@gmail.com \
--to=benavento@gmail.com \
--cc=9fans@9fans.net \
--cc=quanstro@quanstro.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 NNTP newsgroup(s).