Il 02/09/2014 00:56, Peter Crosthwaite ha scritto:
> On Tue, Sep 2, 2014 at 3:43 AM, Peter Maydell
> wrote:
>> On 26 August 2014 01:58, Peter Crosthwaite
>> wrote:
>>> It's not really a common object
>>
>> In what sense isn't it a common object? It's only
>> compiled once, rather than per-targe
On Tue, Sep 2, 2014 at 3:43 AM, Peter Maydell wrote:
> On 26 August 2014 01:58, Peter Crosthwaite
> wrote:
>> It's not really a common object
>
> In what sense isn't it a common object? It's only
> compiled once, rather than per-target. We should
> avoid moving object files from compiled-once
>
On Tue, Sep 2, 2014 at 3:54 AM, Paolo Bonzini wrote:
> Il 01/09/2014 19:43, Peter Maydell ha scritto:
>> On 26 August 2014 01:58, Peter Crosthwaite
>> wrote:
>>> It's not really a common object
>>
>> In what sense isn't it a common object? It's only
>> compiled once, rather than per-target. We s
Il 01/09/2014 19:43, Peter Maydell ha scritto:
> On 26 August 2014 01:58, Peter Crosthwaite
> wrote:
>> It's not really a common object
>
> In what sense isn't it a common object? It's only
> compiled once, rather than per-target. We should
> avoid moving object files from compiled-once
> to com
On 26 August 2014 01:58, Peter Crosthwaite wrote:
> It's not really a common object
In what sense isn't it a common object? It's only
compiled once, rather than per-target. We should
avoid moving object files from compiled-once
to compiled-per-target if we can...
thanks
-- PMM
It's not really a common object and this is needed to give it access to
CONFIG_USER_ONLY definition. Move it to regular obj-y.
Signed-off-by: Peter Crosthwaite
---
Makefile.target | 1 +
qom/Makefile.objs | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/Makefile.target b/
