From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Laurent Vivier" <laurent@vivier.eu>,
"Richard Henderson" <richard.henderson@linaro.org>
Subject: Re: Build for qemu-sh4 broken since 2445971604c
Date: Sat, 15 Feb 2020 15:12:35 +0100 [thread overview]
Message-ID: <b19cff64-a26b-991e-7194-a357d44e58a2@physik.fu-berlin.de> (raw)
In-Reply-To: <1e7c2c17-1907-cc9d-2bad-071bdd09650e@redhat.com>
On 2/15/20 2:53 PM, Philippe Mathieu-Daudé wrote:
> On 2/15/20 11:53 AM, John Paul Adrian Glaubitz wrote:
>> Hi!
>>
>> Currently trying to build qemu-sh4 in static configuration fails with:
>>
>> make[1]: Entering directory '/root/qemu/slirp'
>> make[1]: Nothing to be done for 'all'.
>> make[1]: Leaving directory '/root/qemu/slirp'
>> CC sh4-linux-user/tcg/tcg-op-gvec.o
>> /root/qemu/tcg/tcg-op-gvec.c:298:25: error: unknown type name ‘gen_helper_gvec_5_ptr’; did you mean ‘gen_helper_gvec_4_ptr’?
>> 298 | gen_helper_gvec_5_ptr *fn)
>> | ^~~~~~~~~~~~~~~~~~~~~
>> | gen_helper_gvec_4_ptr
>> make[1]: *** [/root/qemu/rules.mak:69: tcg/tcg-op-gvec.o] Error 1
>> make: *** [Makefile:497: sh4-linux-user/all] Error 2
>
> I believe your build directory is out of date and might have dangling old files.
Yes, this seems to have been the problem, thanks.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
prev parent reply other threads:[~2020-02-15 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-15 10:53 Build for qemu-sh4 broken since 2445971604c John Paul Adrian Glaubitz
2020-02-15 13:53 ` Philippe Mathieu-Daudé
2020-02-15 14:01 ` Philippe Mathieu-Daudé
2020-02-15 14:12 ` John Paul Adrian Glaubitz [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=b19cff64-a26b-991e-7194-a357d44e58a2@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=laurent@vivier.eu \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 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).