10.07.2013, 15:18, "Gisle Vanem" :
> 'int32_t' isn't 'int' for all targets. Some Windows targets have
> it defined as 'signed int' in . So print-nfs.c
> does not compile cleanly; conflicting definition of xid_map_find().
Should both declarations be just "int" then? The function returns either 0 or
"Denis Ovsienko" wrote:
10.07.2013, 15:18, "Gisle Vanem" :
'int32_t' isn't 'int' for all targets. Some Windows targets have
it defined as 'signed int' in . So print-nfs.c
does not compile cleanly; conflicting definition of xid_map_find().
Should both declarations be just "int" then?
That c
11.07.2013, 16:36, "Gisle Vanem" :
> "Denis Ovsienko" wrote:
>
>> 10.07.2013, 15:18, "Gisle Vanem" :
>>> 'int32_t' isn't 'int' for all targets. Some Windows targets have
>>> it defined as 'signed int' in . So print-nfs.c
>>> does not compile cleanly; conflicting definition of xid_map_find().
>