From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] Start Syncing Compilers with Plan 9
Date: Tue, 18 Jun 2019 13:52:15 +0200 [thread overview]
Message-ID: <83FB3F3958782AA1A68266F3AC5AC5FE@felloff.net> (raw)
In-Reply-To: 8FCE1A8D8D8B792BBF325E9251A383C1@eigenstate.org
> I've rebuilt my system with them (for both 386 and amd64), and am
> running with them right now.
try mk nuke. otherwise you would not notice issues with compiling
libraries. thats what i suspect is the reason you missed the OINDEX
bug.
--
cinap
next reply other threads:[~2019-06-18 11:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 11:52 cinap_lenrek [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-06-18 11:41 cinap_lenrek
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=83FB3F3958782AA1A68266F3AC5AC5FE@felloff.net \
--to=cinap_lenrek@felloff.net \
--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).