Re: [PULL v3 00/68] i386, build system, KVM changes for 2023-05-18

[Peter Maydell]

On Fri, 19 May 2023 at 17:51, Paolo Bonzini <pbonzini@redhat.com> wrote:
>
>
>
> Il ven 19 mag 2023, 16:39 Peter Maydell <peter.maydell@linaro.org> ha scritto:
>>
>> On Thu, 18 May 2023 at 12:41, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> > ----------------------------------------------------------------
>> > * kvm: enable dirty ring for arm64
>> > * target/i386: new features
>> > * target/i386: AVX fixes
>> > * configure: create a python venv unconditionally
>> > * meson: bump to 0.63.0 and move tests from configure
>> > * meson: Pass -j option to sphinx
>> > * drop support for Python 3.6
>> > * fix check-python-tox
>> > * fix "make clean" in the source directory
>>
>> Hi; this seems to have broken builds from not-clean on my system.
>> Blowing away the build tree and recreating it from scratch
>> works, as does manually re-running configure,
>> but the Makefile ought to re-run parts of configure
>> etc when it needs to.
>
>
> Can you send your config-host.mak after a failed rebuild? I think what's 
> happening is that the path to meson has changed but Makefile still tries the 
> old one (which could be the system meson in /usr/bin).

Attached; it has
MESON=/mnt/nvmedisk/linaro/qemu-from-laptop/qemu/build/x86-tgts/pyvenv/bin/meson

That meson says:
$ /mnt/nvmedisk/linaro/qemu-from-laptop/qemu/build/x86-tgts/pyvenv/bin/meson
--version
1.1.0

1.1.0 is neither the system meson (which is 0.61.2) nor
the version the build system wants (0.63.0) nor the
version that it complains that it's found (0.61.5),
so I'm not sure what's going on there...

> If so, you should be able to get out of the breakage by adding
>
> MESON=pyvenv/bin/meson
>
> after the "-include config-host.mak" line.

This had no effect (unsurprising given that it's the same meson
as the config-host.mak specifies).

-- PMM

config-host.mak
Description: Text Data