Hi,
This series failed build test on s390x host. Please find the details below.
Message-id: 492245211.936616.1510023015797.javamail.zim...@xes-inc.com
Type: series
Subject: [Qemu-devel] [PATCH] linux-user: Support explicit targets for PowerPC
=== TEST SCRIPT BEGIN ===
#!/bin/bash
# Testing
- Original Message -
> From: "Laurent Vivier"
> Sent: Tuesday, November 7, 2017 9:27:38 AM
> Le 07/11/2017 à 16:20, Aaron Sierra a écrit :
>> - Original Message -
>>> From: "Laurent Vivier"
>>> Sent: Tuesday, November 7, 2017 3:24:52 AM
>>
>>> Le 07/11/2017 à 03:50, Aaron Sierra
- Original Message -
> From: "Peter Maydell"
> Sent: Tuesday, November 7, 2017 9:24:35 AM
> On 7 November 2017 at 15:20, Aaron Sierra wrote:
>> I had that thought, too, as being the cleanest and simplest to implement,
>> but it didn't work out as a practical solution. Having execution de
Le 07/11/2017 à 16:20, Aaron Sierra a écrit :
> - Original Message -
>> From: "Laurent Vivier"
>> Sent: Tuesday, November 7, 2017 3:24:52 AM
>
>> Le 07/11/2017 à 03:50, Aaron Sierra a écrit :
>>> Enable building PowerPC targets supporting a specific CPU, without
>>> having to set QEMU_CPU
- Original Message -
> From: "Peter Maydell"
> Sent: Tuesday, November 7, 2017 3:29:21 AM
> On 7 November 2017 at 06:57, Laurent Vivier wrote:
>> Le 07/11/2017 à 03:50, Aaron Sierra a écrit :
>>> Enable building PowerPC targets supporting a specific CPU, without
>>> having to set QEMU_CP
On 7 November 2017 at 15:20, Aaron Sierra wrote:
> I had that thought, too, as being the cleanest and simplest to implement,
> but it didn't work out as a practical solution. Having execution depend
> on the name of the file would require a lot of tuning of magics, masks,
> and interpreters in /pr
- Original Message -
> From: "Laurent Vivier"
> Sent: Tuesday, November 7, 2017 3:24:52 AM
> Le 07/11/2017 à 03:50, Aaron Sierra a écrit :
>> Enable building PowerPC targets supporting a specific CPU, without
>> having to set QEMU_CPU via the environment. For example these build
>> target
Le 07/11/2017 à 10:29, Peter Maydell a écrit :
> On 7 November 2017 at 06:57, Laurent Vivier wrote:
>> Le 07/11/2017 à 03:50, Aaron Sierra a écrit :
>>> Enable building PowerPC targets supporting a specific CPU, without
>>> having to set QEMU_CPU via the environment. For example these build
>>> ta
On 7 November 2017 at 06:57, Laurent Vivier wrote:
> Le 07/11/2017 à 03:50, Aaron Sierra a écrit :
>> Enable building PowerPC targets supporting a specific CPU, without
>> having to set QEMU_CPU via the environment. For example these build
>> targets (and many more) become available:
>>
>> qem
Le 07/11/2017 à 03:50, Aaron Sierra a écrit :
> Enable building PowerPC targets supporting a specific CPU, without
> having to set QEMU_CPU via the environment. For example these build
> targets (and many more) become available:
>
> qemu-ppc.e500mc qemu-ppc.e500v2 qemu-ppc.e5500 qemu-ppc.e600
>
Le 07/11/2017 à 03:50, Aaron Sierra a écrit :
> Enable building PowerPC targets supporting a specific CPU, without
> having to set QEMU_CPU via the environment. For example these build
> targets (and many more) become available:
>
> qemu-ppc.e500mc
> qemu-ppc.e500v2
> qemu-ppc.e5500
>
Enable building PowerPC targets supporting a specific CPU, without
having to set QEMU_CPU via the environment. For example these build
targets (and many more) become available:
qemu-ppc.e500mc
qemu-ppc.e500v2
qemu-ppc.e5500
qemu-ppc.e600
qemu-ppc.e6500
These (statically compil
12 matches
Mail list logo
