All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL v2 00/11] testing and configure updates
Date: Fri, 18 Dec 2020 16:52:42 +0000	[thread overview]
Message-ID: <87blerqblh.fsf@linaro.org> (raw)
In-Reply-To: <CAFEAcA-UmyTw8Sn5yZrZFxumJRPv-oGg4uL++7av0oTh8fEAMw@mail.gmail.com>


Peter Maydell <peter.maydell@linaro.org> writes:

> On Fri, 18 Dec 2020 at 11:54, Alex Bennée <alex.bennee@linaro.org> wrote:
>>
>>
>> Peter Maydell <peter.maydell@linaro.org> writes:
>> > No, the 'alldbg' build is the one that does do a 'make clean';
>> > the build-not-from-clean build worked (presumably because the
>> > old executable was still left in place from the previous build).
>>
>> Hmm I wonder if it's related to the configure options then. What's your
>> configure setup for that build?
>
> '../../configure' '--cc=ccache gcc' '--enable-debug'
> '--python=python3'

So I did the following:

  git checkout af3f37319cb1e1ca0c42842ecdbd1bcfc64a4b6f
  cd build/bisect
  rm -rf *
  '../../configure' '--cc=ccache gcc' '--enable-debug' '--python=python3'
  make -j30
  make check-qtest

All ok, then

   git checkout pull-testing-171220-2
   cd build/bisect
   make clean
   ag -r "moxie" | wc -l

And sure enough there is a lot of detritus left (21 lines by ag's
counting). However:

  make -j30
  make check-qtest

still passes and doesn't attempt to do anything with moxie. So I'm kind
of stuck as to what to do now? Maybe we can compare detritus and see
what is left in your tree that causes the test system to get confused
and make "clean" really mean it.

  $ ag -l -r "moxie"
  Makefile.ninja
  moxie-softmmu-config-target.h
  qapi/qapi-visit-misc-target.c
  qapi/qapi-events-misc-target.h
  qapi/qapi-types-machine.h
  qapi/qapi-introspect.c
  qapi/qapi-types-misc-target.h
  qapi/qapi-visit-machine.c
  qapi/qapi-visit-misc-target.h
  qapi/qapi-events-misc-target.c
  qapi/qapi-types-machine.c
  meson-info/intro-buildsystem_files.json
  docs/qemu-qmp-ref.7
  docs/interop/qemu-qmp-ref.html
  docs/system/deprecated.html
  docs/system/index.html
  moxie-softmmu-config-devices.mak
  moxie-softmmu-config-devices.h
  build.ninja

I'm surprised about build.ninja and Makefile.ninja? Don't they get
regenerated by the configure?

>
> -- PMM


-- 
Alex Bennée


  reply	other threads:[~2020-12-18 17:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17  9:43 [PULL v2 00/11] testing and configure updates Alex Bennée
2020-12-17 18:48 ` Peter Maydell
2020-12-17 23:41   ` Alex Bennée
2020-12-18 11:12     ` Peter Maydell
2020-12-18 11:53       ` Alex Bennée
2020-12-18 13:40         ` Peter Maydell
2020-12-18 16:52           ` Alex Bennée [this message]
2020-12-18 17:17             ` Alex Bennée
2020-12-18 17:23               ` Paolo Bonzini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87blerqblh.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.