From: "Frank D. Engel, Jr." <fde101@fjrhome.net>
To: 9front@9front.org
Subject: Re: [9front] Port Status
Date: Tue, 5 Jul 2022 06:13:41 -0400 [thread overview]
Message-ID: <4ff0e122-9363-c111-9f09-ab75348b6aee@fjrhome.net> (raw)
In-Reply-To: <A9CFA4A7C8E32F25D6BDFAA9C04CA8E3@eigenstate.org>
All of the issues I am seeing appear to be build issues rather than code
issues.
spim:
cpp: /sys/include/ape/fmt.h:26 ./libc.h:21 ctime.c:1 Could not find
include file <stdarg.h>
68000:
Can't cd 68000: '68000' directory entry not found
68020:
mk: no recipe to make 'cycles.2' in directory /sys/src/libc/68020
sparc:
mk: no recipe to make 'cycles.k' in directory /sys/src/libc/sparc
On 7/4/22 2:36 PM, ori@eigenstate.org wrote:
> Quoth Frank D. Engel, Jr. <fde101@fjrhome.net>:
>> 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-05 10:15 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
2022-07-05 10:13 ` Frank D. Engel, Jr. [this message]
2022-07-05 14:53 ` ori
2022-07-05 18:23 ` adventures in9
2022-07-07 3:16 ` Amavect
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=4ff0e122-9363-c111-9f09-ab75348b6aee@fjrhome.net \
--to=fde101@fjrhome.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).