hi,
what should I care in my kernel structure, so that porting gnu libc will be easy.
you know if gnu libc are ported, then the most application will be easy to port it.
Porting GNU Libc?
Re:Porting GNU Libc?
Except for the OS dependant syscalls (ie video, keyboard etc.) the libc is independant.
If you want to make implementing syscalls easy then try to keep a standard for all the calls:-
Or something which can cover all device calls fairly well
If you want to make implementing syscalls easy then try to keep a standard for all the calls:-
Code: Select all
void read(int start, char *buffer, int size);
Re:Porting GNU Libc?
This particular standard is called POSIX. If you implement it then your OS will be compatible with most Unixes.Therx wrote:If you want to make implementing syscalls easy then try to keep a standard for all the calls:-
Re:Porting GNU Libc?
I have search the internet for POSIX Standard, but I could not found any free docs. did you know one?
Re:Porting GNU Libc?
Try here:
http://www.opengroup.org/onlinepubs/007904975/toc.htm
Free POSIX specifications are hard to come by, since you're supposed to buy a copy.
http://www.opengroup.org/onlinepubs/007904975/toc.htm
Free POSIX specifications are hard to come by, since you're supposed to buy a copy.
Re:Porting GNU Libc?
You're likely to find more information from the Linux man pages than the source. The Linux man pages act as a useful Posix reference (at least where Linux is compliant) whereas the sources are more likely to confuse most people.