Hi,
I am doing a ser build from CVS check-out on a RH based linux with gcc 4.1.1.
The build commands are this.

make clean

make proper

make group_include="standard standard-dep stable mysql"

When I get to any core or module section code which included futexlock.h header, I get the following:

gcc -g -O9 -funroll-loops -Wcast-align -minline-all-stringops -falign-loops -ftree-vectorize -mtune=athlon64 -Wall     -DNAME='"ser"' -DVERSION='"2.1.0-dev17-tcp"' -DARCH='"i386"' -DOS='linux_' -DOS_QUOTED='"linux"' -DCOMPILER='"gcc 4.1.1"' -D__CPU_i386 -D__OS_linux -DSER_VER=2001000 -DCFG_DIR='"/usr/local/etc/ser/"' -DMODS_DIR='"/usr/local/lib/ser/modules/"' -DPKG_MALLOC -DSHM_MEM  -DSHM_MMAP -DDNS_IP_HACK -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER -DUSE_DST_BLACKLIST -DUSE_NAPTR  -DUSE_TLS -DTLS_HOOKS -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024  -DCC_GCC_LIKE_ASM -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_SCHED_SETSCHEDULER -DHAVE_EPOLL -DHAVE_SIGIO_RT -DSIGINFO64_WORKARROUND -DUSE_FUTEX -DHAVE_SELECT -c core_cmd.c -o core_cmd.o
In file included from mem/../futexlock.h:48,
                 from mem/../lock_ops.h:85,
                 from mem/shm_mem.h:76,
                 from core_cmd.c:32:
/usr/include/linux/futex.h:96: error: expected â)â before â*â token
/usr/include/linux/futex.h:98: error: expected â)â before â*â token
make: *** [core_cmd.o] Error 1
=========================================================================

The offending lines came from the  system header  <futex.h>.  The offending lines are:

long do_futex(u32 *uaddr, int op, u32 val, unsigned long timeout, u32 *uaddr2, u32 val2, u32 val3);

extern int handle_futex_death(u32 *uaddr, struct task_struct *curr, int pi);

By pointing to an alternate version of <futex.h> where these lines are commented out
I can compile all the way thru with non-fatal warnings.

My questions are:
1) can anyone tell me what are the equivalent lines in the DEB version where
this code/compile was most recently developed?
2) has anyone got a fix for this error?

..mike..