From: sl@stanleylieber.com
To: 9front@9front.org
Subject: Re: [9front] troubles building from source due to recent changes to libsec
Date: Mon, 16 Oct 2017 19:17:43 -0400 [thread overview]
Message-ID: <789F73A43A466315ABEF03151AC32A7E@mirv.inri.net> (raw)
In-Reply-To: 59dc12a1.5dQhKLFs9mGJhNyB%mikan@waifu.club
> I had some troubles rebuilding the system after doing a sysupdate today.
> The problem was in ape/libsec.h, which didn't have new function definitions
> in it.
This has been fixed by recent commits.
sl
next reply other threads:[~2017-10-16 23:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 23:17 sl [this message]
2017-10-17 19:12 ` Ethan Grammatikidis
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=789F73A43A466315ABEF03151AC32A7E@mirv.inri.net \
--to=sl@stanleylieber.com \
--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).