Porting binutils to other OS

[Alfeiks Kaanoken (MadTirra)]

DJ Delorie wrote:
> "Alfeiks Kaanoken (MadTirra)" <madtirra@jarios.org> writes:
>   
>> I mean, what I need to inject to the source code of binutils to run it
>> in new OS.
>>     
>
> Binutils runs on a wide variety of operating systems, from Linux to
> Windows to DOS to MacOS.  It shouldn't be much trouble to port to any
> other POSIX-based OS.
>
>   
>> have "dummy faked libs" like linux-vdso.so.1 that going on linux (I
>> can wrong, but as I know this is a "kernel" part of system linker),
>>     
>
> The way it works is that the OS either loads the binary itself, or
> loads the binary specified in the header.  That's all.  The dynamic
> loading thing happens when the header says to load the dynamic linker
> instead of the binary.  The dynamic linker is a user-space app that
> loads the actual binary, including resolving all the shared library
> stuff.  The Linux kernel doesn't do any of that.
>
> I think what you said you want and what Linux already does, are very
> similar.
>   
ok
>   
>> Third - I want to compile all OS services, microkernel, applications
>> and so on in native OS, not via toolchain, what the specific stub in
>> binutils do I need ?
>>     
>
> I don't understand.  A "toolchain" can run on the native OS, and what
> "stubs" are you talking about?
>   
Under "toolchain" I mean not native GNU tools (binutils/gcc) that 
installed on linux host to built binaries and shared libs for the other OS.
"stubs" in this context it's a some specific things (linker scripts, 
some source code) related to the new OS.

Thanks.