Re: [PULL v6 000/150] Meson-based build system

[Peter Maydell]

On Wed, 19 Aug 2020 at 19:12, Peter Maydell <peter.maydell@linaro.org> wrote:
>
> On Wed, 19 Aug 2020 at 15:36, Paolo Bonzini <pbonzini@redhat.com> wrote:
> >
> > The following changes since commit d0ed6a69d399ae193959225cdeaa9382746c91cc:
> >
> >   Update version for v5.1.0 release (2020-08-11 17:07:03 +0100)
> >
> > are available in the Git repository at:
> >
> >   https://gitlab.com/bonzini/qemu.git tags/for-upstream
> >
> > for you to fetch changes up to f5b5ef3b9f94d744f514f5469c97d3f80305111e:
> >
> >   docs: convert build system documentation to rST (2020-08-19 10:01:48 
> > -0400)
> >
> > v5->v6: improved incremental build
> >
> > ----------------------------------------------------------------
> > New build system.
> >
> > Missing:
> > * converting configure tests
> > * converting unit tests
> > * converting some remaining parts of the installation
>
> Testing with what I think is the later commit 84264b99322

> Everything else seems to have passed.

Spoke too soon; "make --output-sync -C build/all-linux-static check-tcg"
failed with:

  BUILD   TCG tests for mips-linux-user
  CHECK   debian10
  CHECK   debian-mips-cross
  BUILD   mips-linux-user guest-tests with docker qemu/debian-mips-cross
  RUN     TCG tests for mips-linux-user
  CHECK   debian10
  CHECK   debian-mips-cross
  BUILD   mips-linux-user guest-tests with docker qemu/debian-mips-cross
  RUN     tests for mips
  TEST    threadcount on mips
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
timeout: the monitored command dumped core
Segmentation fault
../Makefile.target:153: recipe for target 'run-threadcount' failed
make[2]: *** [run-threadcount] Error 139
/home/petmay01/linaro/qemu-for-merges/tests/tcg/Makefile.qemu:76:
recipe for target 'run-guest-tests' failed
make[1]: *** [run-guest-tests] Error 2
/home/petmay01/linaro/qemu-for-merges/tests/Makefile.include:450:
recipe for target 'run-tcg-tests-mips-linux-user' failed

Which doesn't look on the face of it like it is a build system
issue, but on the other hand it's not one I've seen before with
the old build system...

thanks
-- PMM