Alfred _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
Re: Problem with gettid() on CentOS 5/gcc 4.1.1
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: CentOS mailing list <centos@xxxxxxxxxx>
- Subject: Re: Problem with gettid() on CentOS 5/gcc 4.1.1
- From: Alfred von Campe <alfred@xxxxxxx>
- Date: Mon, 2 Apr 2007 17:22:59 -0400
- Delivered-to: centos@xxxxxxxxxx
- In-reply-to: <200704021546.l32Fk1v6025203@xxxxxxxxxxxxxxxxxxx>
- References: <200704021546.l32Fk1v6025203@xxxxxxxxxxxxxxxxxxx>
A quick update to this topic. As I alluded to in my original post,
the real issue is that the _syscall0 macro is not defined. Actually,
none of the _syscallx (where x goes from 0 to 6) macros are defined
in /usr/include/linux/unistd.h as they are on a CentOS 4.4 system. I
grep'ed in all of /usr/include and couldn't find any references to
these macros. Have they been deprecated or is this an oversight? At
least one man page (gettid) still references _syscall0...
- References:
- Problem with gettid() on CentOS 5/gcc 4.1.1
- From: Alfred von Campe
- Problem with gettid() on CentOS 5/gcc 4.1.1
- Prev by Date: Re: Re: CentOS 5 Dual Drive Confusion
- Next by Date: Re: NTP
- Previous by thread: Problem with gettid() on CentOS 5/gcc 4.1.1
- Next by thread: Re: Problem with gettid() on CentOS 5/gcc 4.1.1
- Index(es):
 |