9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: a@9srv.net
To: 9fans@9fans.net
Subject: Re: [9fans] Kernel Compiling Problem
Date: Sun, 23 Mar 2008 18:38:48 -0400	[thread overview]
Message-ID: <566d8b1b0b02df04ea949c9ed3f3a353@9srv.net> (raw)
In-Reply-To: <47E6D457.4090802@kix.es>

I'm assuming /386/bin/fossil/fossil does not, in fact, exist.

The fact that the last file completed changes is just a distraction
in this case; I suspect you have $NPROC>1 and mk is parallelizing
its work. I think if you set NPROC=1 before running mk you'll stop
seeing that last file change.

The problem is simply that the kernel mkfiles don't know how to
build things in /sys/src/cmd. The trivial work-around is to build
fossil yourself (cd /sys/src/cmd/fossil && mk install). There's
likely to be other similar binaries needed, so I'd recommend you
'mk install' all of /sys/src/cmd.
Anthony



  reply	other threads:[~2008-03-23 22:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-23 22:06 Rodolfo kix Garci­a
2008-03-23 22:38 ` a [this message]
2008-03-24  8:33   ` Rodolfo kix García 
2008-03-24 14:39     ` Richard Miller
2008-03-24 15:25       ` Rodolfo kix García 
2008-03-24 17:22         ` Richard Miller
2008-03-24 17:42           ` Rodolfo kix García 
2008-03-24 20:58             ` Richard Miller
2008-03-24 23:36               ` Rodolfo kix Garci­a
2008-03-28 14:49                 ` Richard Miller
2008-03-31  8:58               ` david
2008-03-31  9:48                 ` Richard Miller
2008-05-07  9:24                 ` lupin636
2008-05-07 11:04                   ` erik quanstrom
2008-03-24 15:46       ` john
2008-03-24 17:00     ` a

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=566d8b1b0b02df04ea949c9ed3f3a353@9srv.net \
    --to=a@9srv.net \
    --cc=9fans@9fans.net \
    /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).