9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Tiago Natel <tiago.natel@neoway.com.br>
To: 9front@9front.org
Subject: Re: Building pc64 kernel
Date: Tue, 29 Dec 2015 14:34:51 -0200	[thread overview]
Message-ID: <CAEDK68Z6oy4ayX2Pq+ddXT1HLQ3x=irzYgx-+O28X7PcWH8w-A@mail.gmail.com> (raw)
In-Reply-To: <CAEDK68aWmimj5Ah3ngNA8hQguBYLQ8MsEpmiTQGinHcdM1JYFw@mail.gmail.com>

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

haha

Now I see that's well documented in the next section of docs..

*Ignore this email*

Sorry about that!

2015-12-29 14:30 GMT-02:00 Tiago Natel <tiago.natel@neoway.com.br>:

> Hello folks,
>
> Today I've tried to build the pc64 kernel after a fresh install of 9front
> on my laptop.
> I follow the documentation here: http://fqa.9front.org/fqa5.html
>
> But fail to build the pc64 kernel with message below:
>
> mk: don't know how to make '/amd64/bin/paqfs' in directory /sys/src/9/pc64
>
>
> The fresh installation used the pc kernel (objtype=386).
>
> After the help of khm in the #cat-v channel the build was successfully. He
> said that it was needed to *build everything* before build the pc64 kernel
> using objtype=amd64 to populate the paqfs.
>
> The success steps are:
>
> term% cd /sys/src
> term% objtype=amd64 mk install
> term% cd /sys/src/9/pc64
> term% objtype=amd64 mk install
>
> Maybe it's a obvious thing, but not for me (plan9 newbie) and maybe the
> docs should be updated explaining the correct way to change from pc to pc64
> kernel...
>
> Thanks in advance.
>
> []'s
> i4k
>
>

[-- Attachment #2: Type: text/html, Size: 2144 bytes --]

  reply	other threads:[~2015-12-29 16:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-29 16:30 Tiago Natel
2015-12-29 16:34 ` Tiago Natel [this message]
2015-12-29 20:28 sl

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='CAEDK68Z6oy4ayX2Pq+ddXT1HLQ3x=irzYgx-+O28X7PcWH8w-A@mail.gmail.com' \
    --to=tiago.natel@neoway.com.br \
    --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).