From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Mercurial and Plan 9
Date: Fri, 4 Jan 2013 15:56:29 -0600 [thread overview]
Message-ID: <CEB385A1-F9B8-4EBF-A69D-BA37F6E384B7@corpus-callosum.com> (raw)
In-Reply-To: <71A1FC5E-E3DF-4E7E-BB8F-3B99DD2F59C6@gmail.com>
Has anyone completed an APE lib sec yet?
I'm starting to roll an ape build of libsec in as it's needed for
a new Python 2.7.3+ port of Python. I'd gladly take someone else's
mkfile rework to save some time. Libsec is needed to implement a
new _hashlib module, one that doesn't require OpenSSL among others.
The new Python release&build will be pushed out once I clean up
a few more details like getting new builds of Mercurial working.
-jas
On Mar 20, 2012, at 5:11 PM, Federico Benavento <benavento@gmail.com> wrote:
> check, /sys/src/ape/lib/draw/ for some insight
>
> On Mar 14, 2012, at 12:22 PM, Yaroslav wrote:
>
>> Speaking of which... what would be the trick to make libsec visible
>> for an APE source?
>> --
>> - Yaroslav
next prev parent reply other threads:[~2013-01-04 21:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 6:15 Steven Stallion
2012-03-14 6:28 ` Jeff Sickel
2012-03-14 15:17 ` Steven Stallion
2012-03-14 15:22 ` Yaroslav
2012-03-20 22:11 ` Federico Benavento
2013-01-04 21:56 ` Jeff Sickel [this message]
2013-01-04 23:10 ` Steven Stallion
2013-01-05 1:17 ` Charles Forsyth
2013-01-05 2:35 ` Federico G. Benavento
2013-01-07 15:13 ` Yaroslav
2012-03-14 9:19 ` Charles Forsyth
[not found] <CAGGHmKHPkNw5Sf5YfO7TkLVYrZLmbK7jj0nmd2osByyF9sYC2Q@mail.gmail.c>
2012-03-14 12:58 ` erik quanstrom
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=CEB385A1-F9B8-4EBF-A69D-BA37F6E384B7@corpus-callosum.com \
--to=jas@corpus-callosum.com \
--cc=9fans@9fans.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).