Messages in this thread | | | From | "Stephen C. Tweedie" <> | Date | Thu, 22 Apr 1999 22:49:15 +0100 (BST) | Subject | Re: System Call |
| |
Hi,
On 21 Apr 1999 13:35:06 -0300, "Livia Catarina Soares" <liviacatarina@zipmail.com.br> said:
> I also used in the headers : "<linux/unistd.h>".
Make sure you include the linux headers from the new version of the kernel you just built. Either ensure that the /usr/include/linux symlink resolves to that kernel tree or compile with the "-I<new-linux-tree-directory>/include" compiler flag/
> I could not understand why I need to use "syscall3".
Because the _syscall* macros need to know how many arguments to pass to the CPU mechanism used to invoke the system call.
> If I have another system with two, one or other value different from > three. How I must proceed ??
Just use "_syscall2", "_syscall1" or some other syscall* different from "_syscall3".
--Stephen
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |