From: kokamoto@hera.eonet.ne.jp
To: 9front@9front.org
Subject: x509.c for ape in libsec.a
Date: Wed, 1 Jul 2020 14:37:26 +0900 [thread overview]
Message-ID: <01256F7E49252A911BC4AD2B3D7D6F0C@hera.eonet.ne.jp> (raw)
I'm playing with python2.7.6 on 9front.
The ape/libsec.a file for this port makes x509-ape.c instead of x509.c on the fly by the line:
x509-ape.c: ../../../../libsec/port/x509.c
cat ../../../../libsec/port/x509.c | \
sed 's/Tm \*tm = gmtime\(t\)/struct tm *tm0 = gmtime\(\&t\)/;s/tm->/tm0->tm_/g' | \
sed 's/static //g' > x509-ape.c
Essential part is 's/static //g' to use is_seq etc ib cpython/Plan9/_ssl9.c.
Is this OK? for 9front system?
Kenji
PS: I hve permission to port python2.7.6 to 9front from jas.
Porting 2.7.6 is not so bright because it has no implementation of _ctypes() module.
So, this just a play...
next reply other threads:[~2020-07-01 5:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 5:37 kokamoto [this message]
2020-07-02 4:54 ` [9front] " kokamoto
2020-07-02 14:48 ` Ori Bernstein
2020-07-04 0:39 ` kokamoto
2020-07-08 5:19 ` kokamoto
2020-07-09 4:19 ` kokamoto
2020-07-09 4:25 ` ori
2020-07-09 23:31 ` kokamoto
2020-07-10 0:23 ` kokamoto
2020-07-10 0:27 ` ori
2020-07-10 0:53 ` Dr. Kenji Okamoto
2020-07-10 1:31 ` kokamoto
2020-07-10 4:12 ` ori
2020-07-10 4:36 ` kokamoto
2020-07-13 1:39 ` ori
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=01256F7E49252A911BC4AD2B3D7D6F0C@hera.eonet.ne.jp \
--to=kokamoto@hera.eonet.ne.jp \
--cc=9front@9front.org \
/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).