No decent question no decent answer.
PS: this implies that if you actually tell anything about how you have been thinking, doing anything for yourself and possibly trying things, that you will get more helpful replies.
I feel you are awakerd to the question. I only ask the way not the compiling glibc.If i understand and port my syscall it is not the problem. Everybody know to compile the glibc.
I don't understand from where the syscall in glibc interconnected with the kernel.
Probably i think they are in /sysdep/unix folder. But i am not sure.
If you get to the point of wanting to port glibc (and being able to), you will have the answers to these questions. If you made an OS without finding out the basic concept of doing a syscall, or finding out what a package needs, you PROBABLY did not do too much about your own OS to call it your own.
It not so easy than what you answer. Actually the glibc competent for different architecture and the differnet function doesn't work in different architecture and for those architecture we simply write stub in those file where the function resides. I have my own syscall. when my program call syscall then it goes to the library(glibc) from there it interrupt the kernel and saves the regeisters and call the syshandler. My problem is from where in glibc the syscall call the sys handler (kernel code). And what are the basic modification i have to do so that i can use my own syscall. Another thing is my mickrokernel is not linux and it have different architecture and i have to make glibc work for i386.
I expect the answer how i port my syscall to glibc. And the basic Modification
in makefile , configure file etc
PS: I think this is not the right way to Reply the answer.Be cool the person who is asking the question is not genius like you
I am sorry if my words are awakward for you
cheers ;D