Hello,
I am trying to build Singularity RDK 2.0 under a Windows 10 1909 OS with the configure.cmd environment. I tried to build the system using the codebase in this repo's source\base tree, but I got the following:
Found ExHeap
Found ChannelHeap
Endpoint.sg(193,13): error CS1519: Invalid token 'if' in class, struct, or interface member declaration
Endpoint.sg(193,16): error CS1513: } expected
Endpoint.sg(194,23): error CS1530: Keyword new not allowed on namespace elements
and a lot of other errors in the same file
After this, I downloaded the source from CodePlex, releases\2\ long file name in zip format, I was able to build it successfully without any errors. First I built the tiny iso using Tiny.proj, but I have a world iso built as well. Then I started a qemu (used -curses because of my Linux box through SSH):
qemu-system-i386 -cdrom tiny.iso -m 1024 -curses
I got first a message from the bootloader, then debug port 0000, then the bootloader again with loading distribution files, after that a long region dump, and it hangs after BL: entry=00dd6060.
I looked into the bootloader and I saw that the region dump wasn't a sign of error because that has to work like that (blsingularity.cpp) but it didn't load the kernel. I then inserted some debug messages both into the bootloader and HAL's entry point, and it turned out that the HAL, for some reason, can't call g_Main() because the debug messages after that call, and in the kernel's main function didn't appear (I put a WriteLine call immediatelly at the start of kernel main). I think something around the compiler could cause problems, but I don't know. The g_Main() looks like is translated from the kernel.cs's Main() function by Bartok. The same happens under VMWare. Could you tell me please, how could I run the system, or if in this repo this kernel not starting bug is fixed, how can I build the system with this repo's codebase? I would like to try the system, because for me the managed code kernel and concept is very interesting, but couldn't find out how to attach WinDbg to Qemu, so debugging isn't easy for this strange behaviour.
Thank you!
Hello,
I am trying to build Singularity RDK 2.0 under a Windows 10 1909 OS with the configure.cmd environment. I tried to build the system using the codebase in this repo's source\base tree, but I got the following:
Found ExHeap
Found ChannelHeap
Endpoint.sg(193,13): error CS1519: Invalid token 'if' in class, struct, or interface member declaration
Endpoint.sg(193,16): error CS1513: } expected
Endpoint.sg(194,23): error CS1530: Keyword new not allowed on namespace elements
and a lot of other errors in the same file
After this, I downloaded the source from CodePlex, releases\2\ long file name in zip format, I was able to build it successfully without any errors. First I built the tiny iso using Tiny.proj, but I have a world iso built as well. Then I started a qemu (used -curses because of my Linux box through SSH):
qemu-system-i386 -cdrom tiny.iso -m 1024 -curses
I got first a message from the bootloader, then debug port 0000, then the bootloader again with loading distribution files, after that a long region dump, and it hangs after BL: entry=00dd6060.
I looked into the bootloader and I saw that the region dump wasn't a sign of error because that has to work like that (blsingularity.cpp) but it didn't load the kernel. I then inserted some debug messages both into the bootloader and HAL's entry point, and it turned out that the HAL, for some reason, can't call g_Main() because the debug messages after that call, and in the kernel's main function didn't appear (I put a WriteLine call immediatelly at the start of kernel main). I think something around the compiler could cause problems, but I don't know. The g_Main() looks like is translated from the kernel.cs's Main() function by Bartok. The same happens under VMWare. Could you tell me please, how could I run the system, or if in this repo this kernel not starting bug is fixed, how can I build the system with this repo's codebase? I would like to try the system, because for me the managed code kernel and concept is very interesting, but couldn't find out how to attach WinDbg to Qemu, so debugging isn't easy for this strange behaviour.
Thank you!