soz about the pm i thought i was probley a welcome message so i did not read it
i am following a tutorial which was apparently designed mainly for a different os that i have very little experience in also it refer to a program that i have chosen to use a alternatives so as to get it to work with a compiler that was suggested to use and also to avode large amounts of other programmes which i do not need being installed which is what cywin setup.exe tries to do i was previously told in other posts on other forums to include more info i simply include the out put so that if any 1 tried to help me it would be easier for them. i am sorry if u do not like my style of posting
Get error trying to compile the kernel
Last edited by HJED on Mon Sep 10, 2007 4:29 am, edited 1 time in total.
.................................. um what should i put here .............................?..........................................
.....
................
.....
................
I personally do not have much expeirence with Linux (Although I have been thinking of switching...)
Nontheless, this is why I recommend MSVC++ 2005--Its specifically for Windows. The only thing extra thet you may need to do is load in the PE program and execute your kernel. (It does have a limitation of only being able to produce coff and pe exectables)
You can also use DJGPP--Its a GCC port for Windows, and supports more output options then MSVC++ (Such as Elf). It does not come with a nice IDE though.
Nontheless, this is why I recommend MSVC++ 2005--Its specifically for Windows. The only thing extra thet you may need to do is load in the PE program and execute your kernel. (It does have a limitation of only being able to produce coff and pe exectables)
You can also use DJGPP--Its a GCC port for Windows, and supports more output options then MSVC++ (Such as Elf). It does not come with a nice IDE though.
OS Development Series | Wiki | os | ncc
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}
One, stop shouting.
Two, the GCC_Cross-Compiler how-to was written specifically for Windows users (using Cygwin). It merely happens to work just as well for Linux.
Three, of that >800 lines output, only the last ~15 lines are actually useful, which any halfway experienced developer would recognize. The info you did not include was the command line with which you got "past configure", i.e. we are not able to reproduce your problem without guessing and trial & error (making the whole output useless for helping you).
Four, did it occur to you that Cygwin is recommended for a reason, by people who are well aware of the alternatives (which are not simpler)?
Six, the tutorial is simple. In OS development, it is probably among the simplest document you will come across. Failing so utterly to follow such simple advice means that virtually everything you will come across later will give you even more trouble, resulting in many, many more posts to this board and others, people getting annoyed, you getting annoyed, and your great OS idea being swamped in everyday annoyance.
Trying MSVC will not change this. Try yourself at something simpler, some user-space tool or small application that allows you to build experience, both with the tools involved and with communication.
Two, the GCC_Cross-Compiler how-to was written specifically for Windows users (using Cygwin). It merely happens to work just as well for Linux.
Three, of that >800 lines output, only the last ~15 lines are actually useful, which any halfway experienced developer would recognize. The info you did not include was the command line with which you got "past configure", i.e. we are not able to reproduce your problem without guessing and trial & error (making the whole output useless for helping you).
Four, did it occur to you that Cygwin is recommended for a reason, by people who are well aware of the alternatives (which are not simpler)?
Five, stop shouting.i am sorry if u do not like my style of posting
Six, the tutorial is simple. In OS development, it is probably among the simplest document you will come across. Failing so utterly to follow such simple advice means that virtually everything you will come across later will give you even more trouble, resulting in many, many more posts to this board and others, people getting annoyed, you getting annoyed, and your great OS idea being swamped in everyday annoyance.
Trying MSVC will not change this. Try yourself at something simpler, some user-space tool or small application that allows you to build experience, both with the tools involved and with communication.
Every good solution is obvious once you've found it.