Compiling with custom build riscv tools (gcc/binutils) about diosix

[MarcKarasek]

I tried your ripmason branch and it does compile but fails on running qemu ..

qemu-system-riscv64: GLib: g_mapped_file_unref: assertion 'file != NULL' failed

Looks like the file diosix is just 616 bytes long?

[MarcKarasek]

FYI: Version of tools I have compiled
riscv64-unknown-linux-gnu-gcc (GCC) 9.2.0
GNU objcopy (GNU Binutils) 2.32

[diodesign]

Hi -- thanks. There is something strange going on with binutils, which may be my fault.

On a Debian testing/bullseye system with riscv64-linux-gnu-ld version 2.35.2, using the latest development branch (ripmason, commit 6b66e18), I get an assertion failure:

  = note: riscv64-linux-gnu-ld: BFD (GNU Binutils for Debian) 2.35.2 assertion fail elfnn-riscv.c:1765
          riscv64-linux-gnu-ld: BFD (GNU Binutils for Debian) 2.35.2 assertion fail elfnn-riscv.c:1798

On a Fedora 32 system with riscv64-linux-gnu-ld version 2.34-2.fc32, I get a completed, running build of Diosix. I recommend binutils version 2.34 as that seems to work at least. If you get a small Diosix executable then it's likely that an empty ELF file has been generated due to an unreported failure in the build process.

Please try the latest ripmason branch -- git pull it, just clean and then just to build and run it in Qemu, and see if that works for you. I'm working on a way to either build a minimal known-good binutils in the Diosix build tree, figure out what I'm doing that's upsetting binutils version 2.35.x, or write my own minimal linker...

[diodesign]

I'm going to suggest moving this into one issue #17 to get the bottom of the binutils problem -- thanks