9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Jacob Moody <moody@mail.posixcafe.org>
To: 9front@9front.org
Subject: Re: [9front] 9front-8963.f84cf1e60427675514fb056cc1723e45da01e043.amd64.iso vs thinkpad x61t
Date: Fri, 28 Oct 2022 22:32:59 -0600	[thread overview]
Message-ID: <96d5d1bc-b961-94dc-61ce-c0268cabb331@posixcafe.org> (raw)
In-Reply-To: <936DD50B-EBAB-405C-97C1-23E96E1B8081@quintile.net>

While looking over our mkfiles again I do see that we have a 'kernels' target
in /sys/src that builds all of the kernels, but nothing for just the 'current'
kernel. So I thought to add that, and add it to the list of subdirs
we build on a 'install'. This defines the 'current' kernels/boot
programs to those that are for the current objtype.

Now this doesn't do anything for putting the kernel somewhere other then /$objtype.
Most kernel install targets have this notion of $EXTRACOPIES :

install:V:	$p$CONF
	cp $p$CONF /$objtype/
	for(i in $EXTRACOPIES)
		import $i / /n/$i && cp $p$CONF $p$CONF.gz /n/$i/$objtype/

This seems a bit oddly specific, perhaps EXTRACOPIES (or a rename) could be
where someone puts in wherever they need the binary installed to
You'd get something like:

cd /sys/src
KDIRS=/n/9fat mk install

Just some thoughts, maybe this still sucks.

diff c67a1784cc34ffec633b61ad3267e13d162be219 uncommitted
--- a//sys/src/9/mkfile
+++ b//sys/src/9/mkfile
@@ -19,7 +19,13 @@

-installall install:V:
+	for(i in `{grep -l '^objtype='^$objtype */mkfile})@{
+		cd `{basename -d $i}
+		mk install
+	}
 	for(i in $ARCH) @{
 		cd $i
 		mk install
--- a//sys/src/boot/mkfile
+++ b//sys/src/boot/mkfile
@@ -10,7 +10,15 @@

-installall install:V:
+	if(~ $objtype 'amd64')
+		objtype=386
+	for(i in `{grep -l '^objtype='^$objtype */mkfile})@{
+		cd `{basename -d $i}
+		mk install
+	}
 	for(i in $ARCH) @{
 		cd $i
 		mk install
--- a//sys/src/mkfile
+++ b//sys/src/mkfile
@@ -47,12 +47,15 @@

+	boot\
 	echo mk all, install, clean, nuke, release, kernels, or libs

 all install clean nuke:VQ:
-	for (i in $LIBS $SUBSYS $CMDS) @{
+	for (i in $LIBS $SUBSYS $CMDS $KERNS) @{
 		cd $i
 		mk $target
@@ -69,10 +72,10 @@
 	mk clean

-	for (i in 9 boot) @{
+	for (i in $KERNS) @{
 		cd $i
 		mk clean
-		mk install
+		mk installall
 		mk clean

  reply	other threads:[~2022-10-29  4:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26 18:38 Stanley Lieber
2022-10-26 20:04 ` Jacob Moody
2022-10-26 20:24   ` sl
2022-10-27  4:05     ` william
2022-10-27 12:14       ` Jacob Moody
2022-10-27 14:39         ` Stanley Lieber
2022-10-27 16:59           ` umbraticus
2022-10-27 18:13             ` Stanley Lieber
2022-10-28  7:34               ` Steve Simon
2022-10-29  4:32                 ` Jacob Moody [this message]
2022-10-29 20:40                   ` william

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=96d5d1bc-b961-94dc-61ce-c0268cabb331@posixcafe.org \
    --to=moody@mail.posixcafe.org \
    --cc=9front@9front.org \


* 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).