I swear you guys read my mind sometimes... It's creepy.
I just had this very issue, doing the exact same thing, about an hour ago.
Have you tried with -nodefaultlib -noruntime ? Cause that's what works
for me...
I just got *something* to compile with no runtime or std.
Whether or not it actually does anything remains to be seen.
On Fri, 06 Jul 2012 01:53:10 -0500, BLM768 <[email protected]> wrote:
I've been trying to write an OS kernel in D, and I'm having issues with
the runtime. I'm trying to use LDC's -noruntime option, which is
_supposed_ to prevent any runtime calls from being generated, but the
linker keeps complaining about unresolved references to _d_assert_msg
and other runtime functions. It seems that LDC is ignoring the switch
and is generating runtime references anyway. Is there some other way to
force it to stop trying to pull in the runtime? I'd rather not have to
create/link a custom runtime at this point; I don't even have a memory
allocator written, so I really don't want to mess with a runtime yet.
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
