9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Mista Tea <tswoskowiak@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Trouble building Inferno on Linux
Date: Wed,  1 May 2013 12:31:27 +0000	[thread overview]
Message-ID: <527d29b3-3d14-4340-9f1d-bb96373e7805@googlegroups.com> (raw)
In-Reply-To: <7abc443d5b403189e82da97fbc3c907e@proxima.alt.za>

On Friday, April 26, 2013 7:59:39 AM UTC-4, lu...@proxima.alt.za wrote:
> > I checked those files and they are in fact there, they can be read
>
> > and contain data (not zero size). If I run mk without arguments I
>
> > get the same missing include file errors.
>
>
>
> You seem to be assuming that ~ is resolved to a $HOME, which is not
>
> the case in the Plan 9 and Inferno contexts.  Maybe you need to
>
> specify $HOME explicitly?
>
>
>
> ++L

You are correct, it was a newbie mistake on my part. I changed
ROOT=~/inferno to ROOT=/home/usr/inferno and it built. Doh!



  reply	other threads:[~2013-05-01 12:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-26 11:52 Mista Tea
2013-04-26 11:59 ` lucio
2013-05-01 12:31   ` Mista Tea [this message]
2013-04-26 12:08 ` john francis lee

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=527d29b3-3d14-4340-9f1d-bb96373e7805@googlegroups.com \
    --to=tswoskowiak@gmail.com \
    --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).