Hi

I am able to install & build "riscv-pk" and "riscv-isa-sim", and then try out Spike.  Many thank!

> ./configure --prefix=/opt/riscv --enable-multilib
> sudo make linux
Otherwise, I also tried to enable "multilib" when building "riscv-gnu-toolchain" but with no luck. It complained:

> ...
> configure: error: in `/home/webuser/Dev/risc-v/riscv-gnu-toolchain/build-gcc-linux-stage2/riscv64-unknown-linux-gnu/lib32/ilp32/libgomp':
> configure: error: C compiler cannot create executables

And make failed with:

> Makefile:13703: recipe for target 'configure-target-libgomp' failed
> make[2]: *** [configure-target-libgomp] Error 1

Again, any suggestions?

Regards,


Jacob
============================================================
...
checking for riscv64-unknown-linux-gnu-gcc... /home/webuser/Dev/risc-v/riscv-gnu-toolchain/build-gcc-linux-stage2/./gcc/xgcc -B/home/webuser/Dev/risc-v/riscv-gnu-toolchain/build-gcc-linux-stage2/./gcc/ -B/opt/riscv/riscv64-unknown-linux-gnu/bin/ -B/opt/riscv/riscv64-unknown-linux-gnu/lib/ -isystem /opt/riscv/riscv64-unknown-linux-gnu/include -isystem /opt/riscv/riscv64-unknown-linux-gnu/sys-include  -march=rv32imac -mabi=ilp32
checking whether the C compiler works... no
configure: error: in `/home/webuser/Dev/risc-v/riscv-gnu-toolchain/build-gcc-linux-stage2/riscv64-unknown-linux-gnu/lib32/ilp32/libgomp':
configure: error: C compiler cannot create executables
See `config.log' for more details

Makefile:13703: recipe for target 'configure-target-libgomp' failed
make[2]: *** [configure-target-libgomp] Error 1

make[2]: Leaving directory '/home/webuser/Dev/risc-v/riscv-gnu-toolchain/build-gcc-linux-stage2'
Makefile:951: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/webuser/Dev/risc-v/riscv-gnu-toolchain/build-gcc-linux-stage2'
Makefile:304: recipe for target 'stamps/build-gcc-linux-stage2' failed
make: *** [stamps/build-gcc-linux-stage2] Error 2

On Mon, Nov 11, 2019 at 5:52 PM Zhuang, Siwei (Data61, Kensington NSW) <Siwei.Zhuang@data61.csiro.au> wrote:
No, building riscv-isa-sim alone is sufficient if you only need Spike.

seL4 also generates a script called "simulate" in the your build directory.
The script invokes qemu for simulation.

Regards,
Siwei

On Mon, 2019-11-11 at 17:20 -0800, Jacob Yu wrote:
> Thanks, Siwei for the info.  I'll give it a try.
>
> > Running seL4 no longer requires RISC-V tools. In case you want to use
> Spike,
> > I'd suggest building the riscv-isa-sim separately to get the latest code.
>
> Does this require RISC-V tools to build?
>
> Best,
>
>
> Jacob
>
> On Sun, Nov 10, 2019 at 10:58 PM Zhuang, Siwei (Data61, Kensington NSW) <
> Siwei.Zhuang@data61.csiro.au> wrote:
>
> > Hi Jacob,
> >
> > You need to enable multilib when building "riscv-gnu-toolchain".
> >
> >     ./configure --prefix=/path-to-install-toolchain --enable-multilib
> > then
> >     make or make linux
> >
> > Running seL4 no longer requires RISC-V tools. In case you want to use
> > Spike,
> > I'd suggest building the riscv-isa-sim separately to get the latest code.
> >
> > Regards,
> > Siwei
> >
> > On Sun, 2019-11-10 at 15:50 -0800, Jacob Yu wrote:
> > > Hi
> > >
> > > I am trying to build "seL4 tests" for "Spike" platform (the RISC-V
> > > simulator from UC Berkeley) on Ubuntu 18.04.3 LTS, a 64-bit system.
> > >
> > > First of all, I was able to build RISC-V tools with "build.sh" after
> > > manually installing "riscv-gnu-toolchain" from GitHub as well as
> > additional
> > > python modules (future, ply, protobuf).  I then kicked of
> > "../init-build.sh
> > > -DPLATFORM=spike -DRISCV64=TRUE -DSIMULATION=1" from local build
> > directory.
> > > After that, however, "ninja" command complained about "undefined
> > reference
> > > to `__nedf2'". I understand there is no FPU support in "Spike" platform
> > so
> > > a need for "soft-float" module.  Where should I specify "-lsoft-fp"?
> > >
> > > Any suggestions?
> > >
> > > Thanks,
> > >
> > >
> > > Jacob
> > > _______________________________________________
> > > Devel mailing list
> > > Devel@sel4.systems
> > > https://sel4.systems/lists/listinfo/devel