From: Michal Ludvig (michal_at_logix.cz)
Date: Mon 11 Apr 2005 - 00:33:08 BST
Herbert Poetzl wrote:
> On Mon, Apr 11, 2005 at 10:54:38AM +1200, Michal Ludvig wrote:
>>What is the expected behaviour? With glibc I'm getting:
>>ret = 65573
>>However when changed your testcase to use _syscall3() as utils-vserver
>>do I'm getting the same output even with dietlibc.
> ah, that's a good hint, probably _syscall3() is present
> in your includes, could you upload/post the header file
> which contains that (for x86_64)?
It is defined in /usr/include/asm-x86_64/unistd.h of glibc-2.3.3
(included from /opt/dietlibc/include/sys/syscall.h ->
I guess ENSC_SYSCALL macro in m4/ensc_syscall.m4 doesn't correctly
recognize if your system supports "fast" syscalls. Look for 'invocation
method' in your config.log. My one looks like this:
configure:23736: checking for number of syscall 'vserver'
configure:23783: result: 236/glibc
configure:23799: checking for syscall(2) invocation method
configure:23809: result: auto
configure:23814: checking which syscall(2) invocation works
configure:23855: gcc -c -g -O2 -std=c99 -Wall -pedantic -W conftest.c >&5
configure:23861: $? = 0
configure:23865: test -z
|| test ! -s conftest.err
configure:23868: $? = 0
configure:23871: test -s conftest.o
configure:23874: $? = 0
configure:23893: result: fast
Apparently 'fast' = '_syscall3()'
-- * Personal homepage: http://www.logix.cz/michal _______________________________________________ Vserver mailing list Vserver_at_list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver