From: "Alex Bennée" <alex.bennee@linaro.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] check-tcg failure
Date: Fri, 19 Oct 2018 11:25:27 +0100 [thread overview]
Message-ID: <877eiensh4.fsf@linaro.org> (raw)
In-Reply-To: <38a2dbae-42d8-ab2d-2e21-056794945677@linaro.org>
Richard Henderson <richard.henderson@linaro.org> writes:
> On aa64, "cross-compiling" to aa32, with
>
> CC=arm-linux-gnueabihf-gcc
So this is different from ./configure --cross-cc=arch-linux-gnueabihf-
>
> configure determines
>
> aarch64-linux-user/config-target.mak:CROSS_CC_GUEST="aarch64-linux-gnu-gcc"
> aarch64-linux-user/config-target.mak:CROSS_CC_GUEST_STATIC=y
> aarch64-softmmu/config-target.mak:CROSS_CC_GUEST="aarch64-linux-gnu-gcc"
> aarch64-softmmu/config-target.mak:CROSS_CC_GUEST_STATIC=y
> arm-linux-user/config-target.mak:CROSS_CC_GUEST="cc"
> arm-linux-user/config-target.mak:CROSS_CC_GUEST_STATIC=y
> arm-softmmu/config-target.mak:CROSS_CC_GUEST="cc"
> arm-softmmu/config-target.mak:CROSS_CC_GUEST_STATIC=y
>
> which results in
>
> BUILD arm guest-tests with cc
> cc: error: unrecognized command line option ‘-marm’; did you mean ‘-fasm’?
>
> Because of course cc is the aa64 host compiler.
Hmm the build target is determined by check_define which uses $cc so I'm
guessing all those setting cross_FOO to host_cc should be using cc
instead?
In fact looking deeper I'm not sure what HOST_CC is meant to be used
for. We export it to make but the only place I can find it in the source
tree is:
$(feat-dst)gen-features: $(feat-src)gen-features.c
$(call quiet-command,$(HOST_CC) $(QEMU_INCLUDES) -o $@ $<,"CC","$(TARGET_DIR)gen-features")
As part of s390x - weird.
>
>
> r~
--
Alex Bennée
next prev parent reply other threads:[~2018-10-19 10:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 3:54 [Qemu-devel] check-tcg failure Richard Henderson
2018-10-19 10:25 ` Alex Bennée [this message]
2018-10-19 15:55 ` Richard Henderson
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=877eiensh4.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--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).