From: Laurent Vivier <laurent@vivier.eu>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Riku Voipio <riku.voipio@iki.fi>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL v2 0/5] Linux user for 5.0 patches
Date: Tue, 24 Mar 2020 23:10:08 +0100 [thread overview]
Message-ID: <642bfd04-3f58-e1b0-4dde-7bce4dd6d93f@vivier.eu> (raw)
In-Reply-To: <CAFEAcA-LjJ0KsSTe9O=0thuFmc48BYXWOHQ2ZREptSdCMO16CA@mail.gmail.com>
Le 24/03/2020 à 14:14, Peter Maydell a écrit :
> On Tue, 24 Mar 2020 at 12:32, Laurent Vivier <laurent@vivier.eu> wrote:
>> OK, I think there is an existing problem in the build dependencies.
>>
>> Do you use enable all targets ("configure" without parameters)?
>> Do you run make with "all" or "x86_64-linux-user/all"?
>
> This config is
> '../../configure' '--cc=ccache gcc' '--enable-debug' '--static'
> '--disable-system' '--disable-gnutls'
> and it is an incremental build, so just
>
> make --output-sync -C build/all-linux-static -j8
> make --output-sync -C build/all-linux-static check V=1 -j8
> make --output-sync -C ~/linaro/linux-user-test-0.3/ test
> make --output-sync -C build/all-linux-static check-tcg
>
> (it's step 3 that fails here).
>
The problem is introduced by the change I made to be able to bisect
while we move syscall_nr.h from source dir to build dir (as said by
Richard):
4d6a835dea47 ("linux-user: introduce parameters to generate syscall_nr.h")
There is also a new problem introduced by:
5f29856b852d(" linux-user, configure: improve syscall_nr.h dependencies
checking")
that doesn't scan arch variant (it scans ppc64-linux-user but not
ppc64le-linux-user).
The best solution I can propose is to simply remove the piece of code
I've added in configure and let the user to do a "make clean" if the
build fails because of the move of syscall_nr.h from source dir to build
dir.
Any idea?
Thanks,
Laurent
next prev parent reply other threads:[~2020-03-24 22:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 11:16 [PULL v2 0/5] Linux user for 5.0 patches Laurent Vivier
2020-03-24 11:16 ` [PULL v2 1/5] target/i386: Renumber EXCP_SYSCALL Laurent Vivier
2020-03-24 11:16 ` [PULL v2 2/5] linux-user/i386: Split out gen_signal Laurent Vivier
2020-03-24 11:16 ` [PULL v2 3/5] linux-user/i386: Emulate x86_64 vsyscalls Laurent Vivier
2020-03-24 11:16 ` [PULL v2 4/5] linux-user: Add x86_64 vsyscall page to /proc/self/maps Laurent Vivier
2020-03-24 11:17 ` [PULL v2 5/5] linux-user: Flush out implementation of gettimeofday Laurent Vivier
2020-03-24 12:20 ` [PULL v2 0/5] Linux user for 5.0 patches Peter Maydell
2020-03-24 12:32 ` Laurent Vivier
2020-03-24 13:14 ` Peter Maydell
2020-03-24 22:10 ` Laurent Vivier [this message]
2020-03-25 7:41 ` Laurent Vivier
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=642bfd04-3f58-e1b0-4dde-7bce4dd6d93f@vivier.eu \
--to=laurent@vivier.eu \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).