From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Laurent Vivier" <laurent@vivier.eu>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [PATCH 0/4] buildsys: Build quicker (mostly tools and linux-user)
Date: Fri, 10 Jan 2020 17:41:40 +0100 [thread overview]
Message-ID: <8279ff6e-b598-50a0-97ec-2bb7966e0a14@redhat.com> (raw)
In-Reply-To: <d7e57fe9-9c0f-10bf-dfd2-c1832d34cada@vivier.eu>
On 1/10/20 3:03 PM, Laurent Vivier wrote:
> Le 10/01/2020 à 10:17, Philippe Mathieu-Daudé a écrit :
>> Le ven. 10 janv. 2020 09:36, Laurent Vivier <laurent@vivier.eu
>> <mailto:laurent@vivier.eu>> a écrit :
>>
>> Le 09/01/2020 à 16:39, Philippe Mathieu-Daudé a écrit :
>> > In some configuration (linux-user, tools) we can ignore building
>> > various objects (and the libfdt).
>> >
>> > Philippe Mathieu-Daudé (4):
>> > configure: Do not build libfdt is not required
>> > Makefile: Clarify all the codebase requires qom/ objects
>> > Makefile: Restrict system emulation and tools objects
>> > Makefile: Remove unhelpful comment
>> >
>> > configure | 2 ++
>> > Makefile.objs | 31 ++++++++++---------------------
>> > 2 files changed, 12 insertions(+), 21 deletions(-)
>> >
>>
>> Did you test this with all the combinations of --[enable|disable]-tools,
>> --[enable|disable]-user and --[enable|disable]-system
>>
>>
>> I tested 12 of 27 because I thought some sets might overlap but I might
>> have missed something, what combination is giving you problem?
>>
>
> I didn't test your series, but I did this kind of change in the past and
> sometime enabling tools without enabling softmmu can show missing
> objects at build time, or you can also see if tools are built with
> softmmu while tools are disabled.
>
> I used to test with something like
>
> for user in enable disable; do
> for tools in enable disable; do
> for system in enable disable; do
> rm -fr build
> mkdir build && \
> (cd build && \
> ../configure --$user-user \
> --$system-system \
> --$tools-tools && \
> make || exit)
> done
> done
> done
I tested all these 8 combinations, no problem.
prev parent reply other threads:[~2020-01-10 16:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 15:39 [PATCH 0/4] buildsys: Build quicker (mostly tools and linux-user) Philippe Mathieu-Daudé
2020-01-09 15:39 ` [PATCH 1/4] configure: Do not build libfdt is not required Philippe Mathieu-Daudé
2020-01-09 16:33 ` Thomas Huth
2020-01-10 10:04 ` Alistair Francis
2020-01-09 15:39 ` [PATCH 2/4] Makefile: Clarify all the codebase requires qom/ objects Philippe Mathieu-Daudé
2020-01-10 8:13 ` Thomas Huth
2020-01-09 15:39 ` [PATCH 3/4] Makefile: Restrict system emulation and tools objects Philippe Mathieu-Daudé
2020-01-10 8:14 ` Thomas Huth
2020-01-10 8:25 ` Philippe Mathieu-Daudé
2020-01-10 8:34 ` Thomas Huth
2020-01-09 15:39 ` [PATCH 4/4] Makefile: Remove unhelpful comment Philippe Mathieu-Daudé
2020-01-10 8:15 ` Thomas Huth
2020-01-10 8:35 ` [PATCH 0/4] buildsys: Build quicker (mostly tools and linux-user) Laurent Vivier
2020-01-10 9:17 ` Philippe Mathieu-Daudé
2020-01-10 14:03 ` Laurent Vivier
2020-01-10 16:41 ` Philippe Mathieu-Daudé [this message]
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=8279ff6e-b598-50a0-97ec-2bb7966e0a14@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=laurent@vivier.eu \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).