hi villy,

yep, aix uses size_t. 
socklen_t can be defined to size_t  for AIX only (what i did).
If you define the variable you use consequently to socklen_t
you can replace that for systems that have no socklen_t with
int OR whatever the system exspects in that case. 

thats not clean in some sence (redefining a posix type)

I added (inclusive 2 missing prototypes):

#ifdef _AIX
#  ifndef socklen_t
#       define socklen_t size_t
#  endif

#ifdef HAVE_INITGROUPS
        int initgroups (char *User, int BaseGID );
#endif

int setruid (uid_t RUID);
#endif


This cant be the last word because i dont know about 4.3 or <4 
but with that i can compile without problems.


walter


- - - - - - - - - - - - - - Original Message - - - - - - - - - - - - - -
From: Villy Kruse <[EMAIL PROTECTED]>
Subject: Re: LPRng: lprng on AIX
Date: 10/09/02 11:28


>From one of the header files in the apache distribution.
Maybe that would add some more light on this issue.  The
"proper" way is for autoconfig to determine if socklen_t
is available, but that is perhaps an overkill for the time
being.  AIX41 takes int* or size_t* depending on the mood
of the compiler; it is all 32 bit integers anyway.  AIX43
may have 64 bit integers, so that needs a little more care.

 --
 Villy




-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address

If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
with:                           | example:
subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]

If you have major problems,  send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------

Reply via email to