OSDev.org

When i linking object file into elf (Using Win32) it show this error
how can i set ld to support elf_i386 ???


thank you.

Ok! my problem are fixed.
while wait for answer, i still searched 2 days how to link it

and get this link http://cygwin.com/ml/cygwin/2006-11/msg00323.html

i forgot using 'objcopy' (never use it)
-------------
my linking code (fixed)

using on win32 and my code can execute!!!

thank. __/\__

Build a cross compiler. It will save you problems later.

You mean cross-Binutils.

Love4Boobies wrote:You mean cross-Binutils.

Both should be built, since using a host compiler with a cross-linker and assembler sounds like a Bad Idea.

Why are you assuming he's using a compiler?

Love4Boobies wrote:Why are you assuming he's using a compiler?

I just reflexively assumed he was, as it makes sense to me that anybody using assembly (i.e., binutils only or binutils + nasm or some other assembler) would know what they are doing.

I didn't necessarily mean he was interested in GAS either. Maybe he just has the object files and wished to link them. After all, we're in the Everything Else forum.

Exactly, you can use objcopy to create a binary format other than PE (when you use it, you can leave your linker script without binary type information).

Another is about the name of functions and variables, which adds a MinGW "_" before the name of each function. If you do not want that "junk" in your kernel code (and also make your code more compatible with a possible build in Linux), just pass the parameter "-fno-underscore" for GCC.

And you'll end up adding options and more options until you covered all hidden "features" of mingw that will pop up over time, until you find that that particular compiler is inherently broken to do your work.

The cross-compiler is the recommended solution for a reason.

For the second time, cross-Binutils.