Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
hi
i'm working on OSKit and i tryed to fix errors on GCC 4.8.1
but in file: uvm/netbsd/sys/arch/i386/i386/locore.s i give errors that i can't fix them
please note that i'm not familyir with at&t syntax
it is hard to learn
i use cygwin on windows and my cross-compiler is i686-pc-elf
this is the zip file containing the OSKit that i'm working on: http://amir-ramezani.3owl.com/oskit.zip
the errors are like this:
../.././../uvm/netbsd/sys/arch/i386/i386/locore.s:1549: Error: junk at `(OSKIT_NETBSD_UVM_cpu_class)' after expression
how can i fix them?
what should i do?
the makefiles are in build directory
i configured OSKit on that directory
please help: i want to start this project again!
thanks in advance
Last edited by brighteningeyes on Mon Sep 23, 2013 6:32 am, edited 2 times in total.
testing the operating system is very hard when your eyes can't see well
like me and many others
A quick and probably completely wrong guess is that 1) your binutils (assembler) is too old 2) the binutils you use target the wrong operating system, but this file used a OS-specific feature.
Edit: Are you building netbsd with i586-elf? That'd be case 2 and that's batshit wrong. You probably need to use something like i586-netbsd.
Right, the difference between i586-elf and i686-elf doesn't matter. (Note that i686-pc-elf is the same as i686-elf as the -pc part doesn't really matter).
You still miss my main point: Are you building the NetBSD kernel with i686-pc-elf?
(Again, I don't know what oskit is, just a quick debug guess here. Don't mind me if I am wrong)
oskit is some components that is made from freebsd, netbsd, dos, linux and some other things like C library and more things.
this project has not been developed from 2002 until this time
but i want to start it again
you can download it from that link
then you can know what is that
these are errors from that file
i dont know how to fix them
testing the operating system is very hard when your eyes can't see well
like me and many others
i want to compile it for GCC 4.8.1
so, i'm working on it!
i want to start it again: it doesnt developed from 2002
now what is those errors?
it is very important for me!
testing the operating system is very hard when your eyes can't see well
like me and many others
what is rong in that file?
what should i edit?
i ported some of the files to gcc 4.8.1 but i dont know how to port this
because of that: i'm not familyir with at&t syntax!
please help
testing the operating system is very hard when your eyes can't see well
like me and many others
If you can't fix problems like this, then perhaps you should strongly reconsider restarting the OSKit project. You are not giving us enough information to help you, unless we put in a lot of time trying to build OSkit ourselves.
and that error that you see above acur's
some errors like this acur but if you help me, i can fix them
notice i tryed to fix them some times but i dont know what are those errors
i actually like to know what is that error
and how this can be fixed
testing the operating system is very hard when your eyes can't see well
like me and many others
You are not implying we have to tell you how you should fix the errors in the OSKit you're trying to port, are you?
The error may be due to badly defined macro or anything else, without compiling OSKit nobody can tell. I for example do not want to try to port OSKit again.
You're likely to encounter about 400 different errors in OSKit when trying to build with a modern compiler, are you going to come here with each single one of those?
i actually want to port it to gcc 4.8 and write my operating system with it
i dont like my OS source code began to big
i dont want to write everything myself
i want to port for not myself, for every people that who dont want to write everything
i want to build it for this mothern compiler (GCC 4.8.1) because it support's everything in c and c++, it has more features than the old versions of GCC
it is more likable then then the use the old compiler
isn't it?
testing the operating system is very hard when your eyes can't see well
like me and many others
We are willing to help but you need to prove to us that you have the required knowledge for osdev. Asking for help on every single problem you face does not help you out in the long run, neither does it to keep posting the same problem over and over. Osdev is one of the hardest subjects to master and if you cant debug some simple lines of code, you need to go back to userspace and learn how to write and debug programs. I may seem harsh but were not here to sponfeed you, you need to be able to show us what steps you've tried and the steps how you got there.
You need to read the basic information on the osdev wiki pasted above when you log on, mainly the Beginner Mistakes and How To Ask Questions articles
"I think it may be time for some guru meditation"
"Barbarians don't do advanced wizardry"
i know how to debug my OS, i know everything in C and C++ programming languages, i know about intel syntax
but i said above, i dont know about at&t syntax
i use nasm as my assembler
nasm use's intel syntax
i can debug using gdb, write some functions for operating system, and if i dont know something, i go to wiki
sometimes, i dont ask questions here because i'm porting the oskit
i've ported some of the files, but this file feel me very snappish
testing the operating system is very hard when your eyes can't see well
like me and many others
