From: ori@eigenstate.org
To: amavect@gmail.com, 9front@9front.org
Subject: Re: [9front] cmd/mkfile rewrite
Date: Fri, 1 May 2020 11:18:14 -0700 [thread overview]
Message-ID: <D31BE5093203189F0E649FB2E1AC51E9@eigenstate.org> (raw)
In-Reply-To: <E2C67DA5-0663-4651-A875-A345B8B3612F@gmail.com>
> Consider moving the compilers to /sys/src/comp, then.
> Compilers are special enough to get their own dir.
> Then it would be easy to build compiler prereqs first.
The compiler prereqs are libc and libbio -- and I think
we want to build those *twice*. Once to get the compilers
updated, and once to build them with the new compilers.
next prev parent reply other threads:[~2020-05-01 18:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 4:12 Amavect .
2020-04-30 18:49 ` [9front] " cinap_lenrek
2020-05-01 1:00 ` Amavect .
2020-05-01 14:34 ` cinap_lenrek
2020-05-01 17:27 ` Amavect
2020-05-01 18:18 ` ori [this message]
2020-05-01 18:33 ` cinap_lenrek
2020-05-01 23:43 ` Amavect .
2020-05-02 0:04 ` ori
2020-05-12 1:18 ` Amavect .
2020-05-01 18:26 ` 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=D31BE5093203189F0E649FB2E1AC51E9@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
--cc=amavect@gmail.com \
/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).