On 23 February 2018 at 16:33, Stefan Hajnoczi wrote:
> On Tue, Feb 13, 2018 at 02:00:29PM +, Peter Maydell wrote:
>> A persistent build problem we see is where a source file
>> accidentally omits the #include of log.h. This slips through
>> local developer testing because
On Tue, Feb 13, 2018 at 02:00:29PM +, Peter Maydell wrote:
> A persistent build problem we see is where a source file
> accidentally omits the #include of log.h. This slips through
> local developer testing because if you configure with the
> default (log) trace backend trace.h will pull in
On 13 February 2018 at 15:19, Eric Blake wrote:
> On 02/13/2018 08:00 AM, Peter Maydell wrote:
>> +++ b/scripts/tracetool/backend/log.py
>> @@ -20,7 +20,7 @@ PUBLIC = True
>> def generate_h_begin(events, group):
>> -out('#include "qemu/log.h"',
>> +out('#include
On 02/13/2018 06:00 AM, Peter Maydell wrote:
> A persistent build problem we see is where a source file
> accidentally omits the #include of log.h. This slips through
> local developer testing because if you configure with the
> default (log) trace backend trace.h will pull in log.h for you.
>
On 02/13/2018 08:00 AM, Peter Maydell wrote:
A persistent build problem we see is where a source file
accidentally omits the #include of log.h. This slips through
local developer testing because if you configure with the
default (log) trace backend trace.h will pull in log.h for you.
Compilation