On Fri, Nov 1, 2013 at 9:55 PM, Eric Blake wrote:
> On 10/30/2013 10:28 AM, Doug Goldstein wrote:
>> With Mac OS X 10.9, xdrproc_t is no longer defined as:
>>
>> typedef bool_t (*xdrproc_t)(XDR *, ...);
>>
>> but instead as:
>>
>> typdef bool_t (*xdrproc_t)(XDR *, void *, unsigned int);
>>
>> For
On Sat, Nov 2, 2013 at 11:55 AM, Eric Blake wrote:
> On 10/30/2013 10:28 AM, Doug Goldstein wrote:
>> With Mac OS X 10.9, xdrproc_t is no longer defined as:
>>
>> typedef bool_t (*xdrproc_t)(XDR *, ...);
>>
>> but instead as:
>>
>> typdef bool_t (*xdrproc_t)(XDR *, void *, unsigned int);
>>
>> For
On 10/30/2013 10:28 AM, Doug Goldstein wrote:
> With Mac OS X 10.9, xdrproc_t is no longer defined as:
>
> typedef bool_t (*xdrproc_t)(XDR *, ...);
>
> but instead as:
>
> typdef bool_t (*xdrproc_t)(XDR *, void *, unsigned int);
>
> For reference, Linux systems typically define it as:
>
> type
On Wed, Oct 30, 2013 at 11:28 AM, Doug Goldstein wrote:
> With Mac OS X 10.9, xdrproc_t is no longer defined as:
>
> typedef bool_t (*xdrproc_t)(XDR *, ...);
>
> but instead as:
>
> typdef bool_t (*xdrproc_t)(XDR *, void *, unsigned int);
>
> For reference, Linux systems typically define it as:
>
With Mac OS X 10.9, xdrproc_t is no longer defined as:
typedef bool_t (*xdrproc_t)(XDR *, ...);
but instead as:
typdef bool_t (*xdrproc_t)(XDR *, void *, unsigned int);
For reference, Linux systems typically define it as:
typedef bool_t (*xdrproc_t)(XDR *, void *, ...);
The rationale explaine