9front - general discussion about 9front
 help / color / mirror / Atom feed
From: unobe@cpan.org
To: 9front@9front.org
Subject: Re: [9front] [PATCH] mk for only supported archs
Date: Tue, 17 Aug 2021 13:15:12 -0700	[thread overview]
Message-ID: <B55797B5C540F32686A55FB7BA2F2121@smtp.pobox.com> (raw)
In-Reply-To: <A907E11E-0FA0-4067-94F3-B5D35AA8D92B@gmail.com>

Quoth Amavect <amavect@gmail.com>:
> This patch can be made cleaner.
> Just remove spim from $CPUS in mkfile.proto, 

Oy, I can't believe I overlooked that file.  I've updated the patch
(see below).

> and add powerpc detection in cmd/mkfile.

I added a detection to not make dtracy on powerpc and everything else
under /sys/src/cmd built.  It's included in the patch below.  I'm
testing that all the "supported" archs build.  Even tho' ppc cmd now
builds, the two powerpc kernels (mtx and ppc) still fail for different
reasons.  This is the rc script I use:

#!/bin/rc
echo Updating system
sysupdate || exit 'sysupdate failed'
. /sys/lib/rootstub
cd /sys/src
objtypes_default=`{cat mkfile.proto| grep 'CPUS=' | sed -e 's/CPUS=//'}
if (~ $objtypes '')
	objtypes=($cputype `{{for (f in $cputype $objtypes_default) echo $f} | sort | uniq -u})
for (objtype in $objtypes)
	for (mk in nuke all install clean)
		mk $mk || exit 'mk '^$mk^' failed for '^$objtype

cd /sys/man
mk || exit '/sys/man failed'

cd /sys/doc
mk || exit '/sys/doc failed'

cd /sys/src
mk kernels || exit 'mk kernels failed'


> 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 for the link.  I remember you working on this, but didn't
follow it closely.

--- //.git/fs/object/cfebf83947550f3ae730cef4a9b1ab6bf6b8d4f7/tree//sys/src/9/mkfile
+++ /sys/src/9/mkfile
@@ -3,11 +3,13 @@
 	bcm64\
 	cycv\
 	kw\
-	mtx\
+#	multiple build errors: raven.c and trap.c \
+#	mtx\
 	omap\
 	pc\
 	pc64\
-	ppc\
+#	build errors: no recipe to make devce.q \
+#	ppc\
 	sgi\
 	teg2\
 	xen\
--- //.git/fs/object/cfebf83947550f3ae730cef4a9b1ab6bf6b8d4f7/tree//sys/src/boot/zynq/mkfile
+++ /sys/src/boot/zynq/mkfile
@@ -7,6 +7,9 @@
 
 all:V: $TARG
 
+install:V:
+	echo install not supported >[1=2]
+
 clean:V:
 	rm -rf $TARG *.$O
 	@{objtype=$cputype mk -f mkfile.port clean}
--- //.git/fs/object/cfebf83947550f3ae730cef4a9b1ab6bf6b8d4f7/tree//sys/src/cmd/mkfile
+++ /sys/src/cmd/mkfile
@@ -8,8 +8,9 @@
 YFLAGS=-d
 
 NOTSYS=sml|dup|.+\..+
+NOTPOWER=|dtracy
 PCONLY=|vmx
-NOMK=$NOTSYS`{~ $objtype (386 amd64) || echo $PCONLY}
+NOMK=$NOTSYS$NOTPOWER`{~ $objtype (386 amd64) || echo $PCONLY}
 
 cpuobjtype=`{sed -n 's/^O=//p' /$cputype/mkfile}
 DIRS=`{echo */mkfile | sed 's,/mkfile *,\n,g' | grep -v '^('$NOMK')$'}
--- //.git/fs/object/cfebf83947550f3ae730cef4a9b1ab6bf6b8d4f7/tree//sys/src/mkfile.proto
+++ /sys/src/mkfile.proto
@@ -2,8 +2,8 @@
 # common mkfile parameters shared by all architectures
 #
 
-OS=05678qv
-CPUS=spim arm arm64 amd64 386 power mips
+OS=5678qv
+CPUS=arm arm64 amd64 386 power mips
 CFLAGS=-FTVw
 LEX=lex
 YACC=yacc


  reply	other threads:[~2021-08-18  9:02 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 [this message]
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=B55797B5C540F32686A55FB7BA2F2121@smtp.pobox.com \
    --to=unobe@cpan.org \
    --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).