9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Amavect <amavect@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] mk for only supported archs
Date: Sun, 22 Aug 2021 10:13:09 -0500	[thread overview]
Message-ID: <20210822101309.6a39e399@spruce.localdomain> (raw)
In-Reply-To: <241C0FB9D5249020D1FED63DFC63D664@felloff.net>

[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]

On Sun, 22 Aug 2021 16:33:37 +0200
cinap_lenrek@felloff.net wrote:

> why are we removing spim from archs?

spim does not build, and we have no working spim kernel.
Thus, there is no reason to include spim for mk installall.
Attached is my changes.

Thanks,
Amavect


From: Amavect <amavect@gmail.com>
Date: Sun, 22 Aug 2021 15:05:38 +0000
Subject: [PATCH] mkfile.proto: remove spim and $MK, organize $CPUS

`objtype=spim mk install` does not build, and we have no working kernel.
$MK is useless, and is not used anywhere in the system.
Reorder $CPUS in lexographic order for fun.
---
diff 8c796bf8b9c10a0845717c47af908e47dfe14482
2106158cb0e529e550a65e51b21b66cc12d580b0 ---
a/sys/src/mkfile.proto	Thu Aug 19 23:07:37 2021 +++
b/sys/src/mkfile.proto	Sun Aug 22 10:05:38 2021 @@ -3,11 +3,10 @@
 #
 
 OS=05678qv
-CPUS=spim arm arm64 amd64 386 power mips
+CPUS=386 amd64 arm arm64 mips power
 CFLAGS=-FTVw
 LEX=lex
 YACC=yacc
-MK=/bin/mk
 
 # recursive mk will have these set from the parent
 # this is never what we want.  clear them

[-- Attachment #2.1: Type: text/plain, Size: 313 bytes --]

from postmaster@1ess:
The following attachment had content that we can't
prove to be harmless.  To avoid possible automatic
execution, we changed the content headers.
The original header was:

	Content-Type: text/x-patch
	Content-Transfer-Encoding: 7bit
	Content-Disposition: attachment; filename=mkfileproto.diff

[-- Attachment #2.2: mkfileproto.diff.suspect --]
[-- Type: application/octet-stream, Size: 766 bytes --]

From: Amavect <amavect@gmail.com>
Date: Sun, 22 Aug 2021 15:05:38 +0000
Subject: [PATCH] mkfile.proto: remove spim and $MK, organize $CPUS

`objtype=spim mk install` does not build, and we have no working kernel.
$MK is useless, and is not used anywhere in the system.
Reorder $CPUS in lexographic order for fun.
---
diff 8c796bf8b9c10a0845717c47af908e47dfe14482 2106158cb0e529e550a65e51b21b66cc12d580b0
--- a/sys/src/mkfile.proto	Thu Aug 19 23:07:37 2021
+++ b/sys/src/mkfile.proto	Sun Aug 22 10:05:38 2021
@@ -3,11 +3,10 @@
 #
 
 OS=05678qv
-CPUS=spim arm arm64 amd64 386 power mips
+CPUS=386 amd64 arm arm64 mips power
 CFLAGS=-FTVw
 LEX=lex
 YACC=yacc
-MK=/bin/mk
 
 # recursive mk will have these set from the parent
 # this is never what we want.  clear them


  reply	other threads:[~2021-08-22 17:07 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
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 [this message]
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=20210822101309.6a39e399@spruce.localdomain \
    --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).