QEMU for RISC-V lbForth

[Phi-Ho]

Hello,

Now that I got qemu-system-riscv32.exe and qemu-system-riscv64.exe, which emulator (elf file and command line to invoke qemu) is needed to properly run RISC-V lbForth

Thanks for sharing.

Regards,

phiho

[larsbrinkhoff]

I believe you should use qemu-user-riscv32, but since I don't have this set up properly now I'm not sure.

[Phi-Ho]

Hi, Do you still have a runnable RISC-V lbForth on your computers to verify reported issues ? Regards, phiho

…

On Tue, Nov 24, 2020 at 12:22 PM Lars Brinkhoff ***@***.***> wrote: I *believe* you should use qemu-user-riscv32, but since I don't have this set up properly now I'm not sure. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#95 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABDAWSXCZ7BQ3D6L77YYEP3SRPTT3ANCNFSM4UBBBF6Q> .

[larsbrinkhoff]

Yes. I built it now and ran the tests successfully. Attaching a zip file.
riscv.zip

[Phi-Ho]

Hi, Thank you very much. Would you please share the environment where you just built the attached RISC-V lbForth so that I can build it on my machine. Regards, phiho

…

On Tue, Nov 24, 2020 at 3:14 PM Lars Brinkhoff ***@***.***> wrote: Yes. I built it now and ran the tests successfully. Attaching a zip file. riscv.zip <https://github.com/larsbrinkhoff/lbForth/files/5592401/riscv.zip> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#95 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABDAWSQ76N5QWA2H2RSNARTSRQH3BANCNFSM4UBBBF6Q> .

[larsbrinkhoff]

I built it like this, in two steps:

make clean all TARGET=x86 OS=linux
make TARGET=riscv OS=linux

If your host is Windows, use OS=windows on the first line instead.

[larsbrinkhoff]

QEMU isn't needed for building a target Forth. It's just needed for running of testing the target.

[Phi-Ho]

Hi, Thank you for your response, I could build it on my machine but still cannot run ịt I would like to run the tests on my machine. How did you do it on your machine, what tests did you do? Regards,

…

On Wed, Nov 25, 2020 at 2:22 AM Lars Brinkhoff ***@***.***> wrote: QEMU isn't needed for *building* a target Forth. It's just needed for running of testing the target. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#95 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABDAWSR3IOU6Y2CEF3AIXEDSRSWBZANCNFSM4UBBBF6Q> .

[larsbrinkhoff]

The test are run with "make check TARET=riscv OS=linux". The RISC-V binary is run using the script targets/riscv/run.sh. As you can see, you will need something like riscv32-linux-user/qemu-riscv32. Since it was many years ago I worked on this, I can't say how to do this today.

[Phi-Ho]

Hi, Thank you so much for your clarification. It is great that your RISC-V environment is still running I am still struggling. Regards, phiho

…

On Wed, Nov 25, 2020 at 8:21 AM Lars Brinkhoff ***@***.***> wrote: The test are run with "make check TARET=riscv OS=linux". The RISC-V binary is run using the script targets/riscv/run.sh. As you can see, you will need something like riscv32-linux-user/qemu-riscv32. Since it was many years ago I worked on this, I can't say how to do this today. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#95 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABDAWSWLHTWSUG6CRI7BOMTSRUAEDANCNFSM4UBBBF6Q> .