[uClibc]UNIFIED_SYSCALL - does it work?

[Thomas Cameron]

Hello,
	If you are compiling into a PIC library, then I don't believe it
will work at _all_.  I haven't tested the unstable branch without PIC
on, but I know that the stable one should compile up just fine.  You may
want to watch out though, because the compiler will throw up LOTS of
errors.  I find that using UNIFIED_SYSCALL=yes produces such an
insignificant gain that it isn't worth using.  I'm sure there are
exceptions for that rule, but I can't imagine that it is usefull for
general use.  Good luck!

-Thomas Cameron


-----Original Message-----
From: Oliver Dawid [mailto:od at fet.uni-hannover.de] 
Sent: Wednesday, January 23, 2002 1:54 AM
To: uclibc at uclibc.org
Subject: [uClibc]UNIFIED_SYSCALL - does it work?


hi,

i tested the UNIFIED_SYSCALL = yes on my box, but the compilation
aborted. the linker copmplains about a symbol that could not be found:

gcc -Wall -Os  -march=i386 -mpreferred-stack-boundary=2
  -malign-functions=0 -malign-jumps=0 -malign-loops=0
  -fno-builtin -nostdinc
  -pipe -nostdinc -I../../../../include
  -I/usr/local/lib/gcc-lib/i686-pc-linux-gnu/2.95.3/include
  -I. -D_LIBC  -DNDEBUG  -DL___rt_sigaction syscalls.c -c -o
  __rt_sigaction.o
syscalls.c:1269: parse error before `__STR_NR___rt_sigaction'
make[4]: *** [__rt_sigaction.o] Fehler 1

switching UNIFIED_SYSCALL off, everything goes well.

od

-- 
   Oliver Dawid * od at fet.uni-hannover.de *
http://www.fet.uni-hannover.de/~od/

_______________________________________________
uClibc mailing list
uClibc at uclibc.org
http://uclibc.org/mailman/listinfo/uclibc