Stand Alone Compiler?

I'll use Windows as an example since I can guestimate more about it.

Say you make a compiler using java which runs from command line like:
java main.Main <filename>

The heirarchy is like this right?
your program is interpreted by java
java is of type .exe which is interpreted by the windows compiler/interpreter
the windows compiler/interpreter interprets to some sort of machine level code to execute the program

My question is, short of making up a new machine level code, could a programming language used for something like an OS kernel be made that is self sufficient? Would you have to make the compiler from assembly or something so that you would only need the compiler and the assembly libraries in the kernel? I cant seem to figure out how you could make your compiler/language a stand alone executable without having to have the system containing dependencies for other languages like C or Java or something.

I think you have some misconceptions regarding how programs are executed and what compilers do. The program "java" is a binary executable, which means it is run directly on the hardware without an interpreter in between.

When you compile, say, a C program, the compiler creates a binary executable which runs directly on the hardware. Most of the time, the program must still rely on the operating system for certain resources. Of course, this is different for a kernel: the kernel has to access those resources directly and in turn provide an abstract interface to them for user programs.

Definitely, I am confused. I think I confused myself more with that post than before. My question is: What is necessary (if possible) to have a basic operating system kernel built off of 1-2 languages, one that is created by the developer and I guess the other that is machine level code. I think that makes a bit more sense and is what I'm trying to ask.

**sorry for my newbie-ness

If what you're trying to say is 'can you develop a kernel in a high level language?', the answer is yes. There are compilers for smalltalk, scheme, haskell and many other languages that compile to kernel code with their own library functions (since you can't just link against glibc etc.)

Alright, definitely bit off more than I can chew with this one, but I think I know what to do now. Thanks for your comments, hope to be back with some sort of coherent, useful information.