From: Amavect <amavect@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] mk for only supported archs
Date: Tue, 17 Aug 2021 10:53:30 -0500 [thread overview]
Message-ID: <A907E11E-0FA0-4067-94F3-B5D35AA8D92B@gmail.com> (raw)
In-Reply-To: <8FA58107FDEFD99779044B4B0D7E6B8B@smtp.pobox.com>
This patch can be made cleaner.
Just remove spim from $CPUS in mkfile.proto,
and add powerpc detection in cmd/mkfile.
I have work on revising the system mkfiles.
It's pretty old because there felt like a lack of interest,
and I took a sizeable break.
Some people had recently encouraged me to try again,
so I will make a new patch request soon.
I have a few changes that I want to push later tonight before doing so.
Feel free to look through it as it is and provide any thoughts.
I don't believe I have any fix for mk kernels yet.
https://git.sr.ht/~amavect/mkfilechanges
Thanks,
Amavect
next prev parent reply other threads:[~2021-08-18 9:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 14:00 unobe
2021-08-17 15:53 ` Amavect [this message]
2021-08-17 20:15 ` unobe
2021-08-21 8:27 ` unobe
2021-08-22 14:15 ` cinap_lenrek
2021-08-22 14:33 ` cinap_lenrek
2021-08-22 15:13 ` Amavect
2021-08-18 3:00 ` ori
2021-08-18 22:47 ` unobe
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=A907E11E-0FA0-4067-94F3-B5D35AA8D92B@gmail.com \
--to=amavect@gmail.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).