Re: [Qemu-devel] [PULL 00/24] MTTCG Base enabling patches with ARM enablement

[Christian Borntraeger]

On 02/27/2017 10:11 AM, Alex Bennée wrote:
> 
> Christian Borntraeger <address@hidden> writes:
> 
>> On 02/25/2017 10:14 PM, Peter Maydell wrote:
>>> On 24 February 2017 at 11:20, Alex Bennée <address@hidden> wrote:
>>>> The following changes since commit 
>>>> 2d896b454a0e19ec4c1ddbb0e0b65b7e54fcedf3:
>>>>
>>>>   Revert "hw/mips: MIPS Boston board support" (2017-02-23 18:04:45 +0000)
>>>>
>>>> are available in the git repository at:
>>>>
>>>>   https://github.com/stsquad/qemu.git tags/pull-mttcg-240217-1
>>>>
>>>> for you to fetch changes up to ca759f9e387db87e1719911f019bc60c74be9ed8:
>>>>
>>>>   tcg: enable MTTCG by default for ARM on x86 hosts (2017-02-24 10:32:46 
>>>> +0000)
>>>>
>>>> ----------------------------------------------------------------
>>>> This is the MTTCG pull-request as posted yesterday.
>>>>
>>>> ----------------------------------------------------------------
>>>
>>> Applied, thanks.
>>>
>>> -- PMM
>>>
>>
>> This seems to trigger
>>
>> /home/cborntra/REPOS/qemu/vl.c: In function ‘main’:
>> /home/cborntra/REPOS/qemu/vl.c:3700:18: error: ‘QEMU_OPTION_accel’ 
>> undeclared (first use in this function)
>>              case QEMU_OPTION_accel:
>>                   ^~~~~~~~~~~~~~~~~
>> /home/cborntra/REPOS/qemu/vl.c:3700:18: note: each undeclared identifier is 
>> reported only once for each function it appears in
>>
>>
>> on s390.
> 
> Is this for softmmu compilation? I'll have a look but I'll have to set
> up some s390 images to test so you might beat me to it if you have real
> hardware around.

Ok, my fault. I seem to have run make in the code folder somewhen in the past,
which created an qemu-options.def file in the source folder. When doing the 
rebuild in my build folder, it used qemu-options.def from the source folder
and not from the build folder.

With a clean restart everything seems fine

Christian