Hi,
in the meantime I have found the problem, it is was just a problem with library ordering. I had to add -lg before -lgloss. It seems that by default all implicitly linked libraries like libg are linked after the explicitly invoked.
Just for completeness I just want to tell you why I want add syscalls:
My project is a own RISC-V implementation running on an FPGA. It contains a boot loader which also implements a simple syscall interface like the proxy kernel in spice (In fact I just copied the syscall interface of riscv-pk into it and adapted it).
The idea was that I can run the same binaries on spike and on the harware, this was a handy feature in the beginning. In the meantime this is not so important anymore, I’m considering removing the the syscall interface to reduce the size of the bootloader.
In general the project is more close to an embedded platform, I did not plan to make it Linux capable. I’m currently in the process of publishing my work, and therefore I want to make it easy for people to get started. So I’m testing your toolchain as one option for a precompiled toolchain. In contrast to the SiFive downloads it is much smaller, I think because it is missing all the Linux stuff. This is nice e.g. for docker containers, etc.
On the other hand I notice the fragmentation in the tool chains. Your variant is a bit different from SiFives. What I’m also missing is any form of “Release notes” for the toolchain. In the past I once in a while updated my toolchain from the original repo and recompiled. It was then always a nice journey to adapt all my code to compile with the new build. In the last months thinks seem to have settled and are more stable.
Today I adapted all my Makefiles that they can work with riscv32-unknown-elf* (which my own builds still use…), riscv64-unknown-elf and now also riscv-none-embed
Nevertheless many thanks for your effforts, generally your toolchain build fits my needs very well.