>>> On 22.06.16 at 14:33, wrote:
> On 22/06/16 13:26, Jan Beulich wrote:
> On 22.06.16 at 13:24, wrote:
>>> Make use of C standard freestanding headers, to avoid bugs in our own local
>>> versions of inttypes.h and booleans.
>> While the motivation to do this is certainly a good one, I see po
On 22/06/16 13:26, Jan Beulich wrote:
On 22.06.16 at 13:24, wrote:
>> Make use of C standard freestanding headers, to avoid bugs in our own local
>> versions of inttypes.h and booleans.
> While the motivation to do this is certainly a good one, I see possible
> problems resulting from this. T
>>> On 22.06.16 at 13:24, wrote:
> Make use of C standard freestanding headers, to avoid bugs in our own local
> versions of inttypes.h and booleans.
While the motivation to do this is certainly a good one, I see possible
problems resulting from this. These are best demonstrated by
compiling a C
Make use of C standard freestanding headers, to avoid bugs in our own local
versions of inttypes.h and booleans.
Andrew Cooper (6):
xen/build: Allow the use of C freestanding headers
xen/build: Use the system stdarg.h header
xen/build: Use the system stdint.h header
xen/build: Use the syst
