Subject: Re: [9front] Port Status
Date: Mon, 04 Jul 2022 14:36:30 -0400 [thread overview]
Message-ID: <A9CFA4A7C8E32F25D6BDFAA9C04CA8E3@eigenstate.org> (raw)
Quoth Frank D. Engel, Jr. <email@example.com>:
> I just tried to do updated builds for all of the architectures listed in
> the man page for the compiler.
> The ports for spim, 68000, 68020 and sparc currently appear to be broken.
> All of them appear to be failing when trying to build libc, though the
> specific error varies. Two of them are missing recipes to build "cycles".
> Not a big issue for me right now, but thought I would bring some
> attention to it in any case.
It probably makes sense to delete them, unless someone can step up
with hardware to try them on.
I sure as heck can't test.
next prev parent reply other threads:[~2022-07-04 18:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 1:25 Frank D. Engel, Jr.
2022-07-04 18:36 ` ori [this message]
2022-07-05 10:13 ` Frank D. Engel, Jr.
2022-07-05 14:53 ` ori
2022-07-05 18:23 ` adventures in9
2022-07-07 3:16 ` Amavect
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).