1) pthreads_op.c calls pthread_create() and pthread_detach().
Find out which AIX library implements these functions, and the
corresponding header file should be included.
2) Judging from the error message below, I doubt if the system was
corrupted in some way
/usr/include/pthread.h:666: error: expected ')' before '*'
token
Try compile the following simple program and see if it passes.
#include <pthread.h>
int main()
{
pthread_t lthread;
int ret = 0;
return(ret);
}
On Monday, August 27, 2012 8:33:23 AM UTC-7, dkoleary wrote:
>
> Hi;
>
> Trying to install ossec agent on an old aix 5.3.0 box w/gcc 4.1.1
> installed. Compile seems to get most of the way through and chokes on
> 'making shared' in pthread.h:
>
> make[1]: Entering directory `/db2/crash/ossec-hids-2.6/src/shared'
> gcc -c -g -Wall -I../ -I../headers -DDEFAULTDIR=\"/var/ossec\" -DCLIENT
> -DUSE_OPENSSL -DAIX -DHIGHFIRST -DARGV0=\"shared-libs\"
> -DXML_VAR=\"var\" -DOSSECHIDS *.c
> In file included from pthreads_op.c:15:
> /usr/include/pthread.h:666: error: expected ')' before '*' token
> /usr/include/pthread.h:669: error: expected ')' before '*' token
> /usr/include/pthread.h:672: error: expected ')' before '*' token
> /usr/include/pthread.h:675: error: expected ')' before '*' token
> /usr/include/pthread.h:678: error: expected ')' before '*' token
> /usr/include/pthread.h:686: error: expected ')' before '*' token
> /usr/include/pthread.h:689: error: expected ')' before '*' token
> /usr/include/pthread.h:692: error: expected ';', ',' or ')' before '*'
> token
> /usr/include/pthread.h:695: error: expected ')' before '*' token
> /usr/include/pthread.h:703: error: expected ')' before '*' token
> /usr/include/pthread.h:707: error: expected ')' before '*' token
> /usr/include/pthread.h:710: error: expected ')' before '*' token
> make[1]: *** [shared] Error 1
> make[1]: Leaving directory `/db2/crash/ossec-hids-2.6/src/shared'
>
> I saw a post from 2007 in which someone circumvented this problem by
> commenting out all the pthread.h includes in the source. I'm not opposed
> to doing that; however, I don't know what I'll be disabling by doing so.
> Does anyone know of a more recent fix to this problem?
>
> Thanks.
>
> Doug O'Leary
>
