9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Cyber Fonic <cyberfonic@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] tinyemu - riscv emulator
Date: Tue, 9 Nov 2021 13:55:54 +1100	[thread overview]
Message-ID: <CALj3Nd3Y8KCZ0EN2RVAGo3uCjV=1HBOt4JaxxEzu52JUnU35_w@mail.gmail.com> (raw)
In-Reply-To: <9313f318fc6f0a1700bd2ed858cbf4c6@hamnavoe.com>

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

Thank you for the nudges towards the right direction.
Self-inflicted confusion :  I'm running 9vx and forgot that I was mk'ing an
emulator to run within an emulator.

After a lot of fiddling with libraries, dependencies I got tinyemu to
compile and run.

When I execute:  tinyemu bridge.cfg
It can't find *9tecpu.bin*.
I presume that it's the Plan9 kernel.
Any suggestions as to what steps to take in order to generate it?





On Tue, 9 Nov 2021 at 02:40, Richard Miller <9fans@hamnavoe.com> wrote:

> > The make command failed with dependency on slirp module.
> 
> I don't think plan 9 has a 'make' command. If you just run 'mk'
> on plan 9 in the tinyemu directory, it uses the mkfile there
> and there's no slirp dependency.
> 

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T8096c17a051960c4-M9f3fab43d025663812251b28
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

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

  reply	other threads:[~2021-11-09  2:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bc57352c75e257ec117ce59b4c498ab1@hamnavoe.com>
2021-11-07 23:23 ` Cyber Fonic
2021-11-08 10:44   ` Richard Miller
2021-11-08 13:12     ` Cyber Fonic
2021-11-08 15:39       ` Richard Miller
2021-11-09  2:55         ` Cyber Fonic [this message]
2021-11-09 14:52           ` Richard Miller
2021-11-09 15:03           ` Richard Miller
2021-11-10  1:47             ` Cyber Fonic
2021-11-11 19:29               ` Richard Miller

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='CALj3Nd3Y8KCZ0EN2RVAGo3uCjV=1HBOt4JaxxEzu52JUnU35_w@mail.gmail.com' \
    --to=cyberfonic@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).