From: Wainer dos Santos Moschetta <wainersm@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>, qemu-devel@nongnu.org
Cc: "Fam Zheng" <fam@euphon.net>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH v3] travis-ci: Disable C++ optional objects on AArch64 container
Date: Tue, 9 Feb 2021 09:53:28 -0300 [thread overview]
Message-ID: <ebdddd92-cb51-e8b9-dfc0-fbce35015eb3@redhat.com> (raw)
In-Reply-To: <20210207121239.2288530-1-f4bug@amsat.org>
On 2/7/21 9:12 AM, Philippe Mathieu-Daudé wrote:
> Travis-CI seems to have enforced memory limit on containers,
> and the 'GCC check-tcg' job started to fail on AArch64 [*]:
>
> [2041/3679] Compiling C++ object libcommon.fa.p/disas_nanomips.cpp.o
> FAILED: libcommon.fa.p/disas_nanomips.cpp.o
> {standard input}: Assembler messages:
> {standard input}:577781: Warning: end of file not at end of a line; newline inserted
> {standard input}:577882: Error: unknown pseudo-op: `.lvl35769'
> {standard input}: Error: open CFI at the end of file; missing .cfi_endproc directive
> c++: fatal error: Killed signal terminated program cc1plus
> compilation terminated.
>
> Until we have a replacement for this job on Gitlab-CI, disable
> compilation of C++ files by forcing the c++ compiler to /bin/false
> so Meson build system can not detect it:
>
> $ ../configure --cxx=/bin/false
>
> Compilation
> C compiler: cc
> Host C compiler: cc
> C++ compiler: NO
>
> [*] https://travis-ci.org/github/qemu/qemu/jobs/757819402#L3754
>
> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> ---
> v3: Aarch -> AArch
> v2: Link to first line with error, describe Meson
>
> Supersedes: <20210206200537.2249362-1-f4bug@amsat.org>
> ---
> .travis.yml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Either disable then migrate to gitlab or going straight to the later,
works for me.
Reviewed-by: Wainer dos Santos Moschetta <wainersm@redhat.com>
>
> diff --git a/.travis.yml b/.travis.yml
> index 5f1dea873ec..b4b2d66fa4b 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -261,7 +261,7 @@ jobs:
> - genisoimage
> env:
> - TEST_CMD="make check check-tcg V=1"
> - - CONFIG="--disable-containers --target-list=${MAIN_SOFTMMU_TARGETS}"
> + - CONFIG="--disable-containers --target-list=${MAIN_SOFTMMU_TARGETS} --cxx=/bin/false"
> - UNRELIABLE=true
>
> - name: "[ppc64] GCC check-tcg"
next prev parent reply other threads:[~2021-02-09 12:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 12:12 [PATCH v3] travis-ci: Disable C++ optional objects on AArch64 container Philippe Mathieu-Daudé
2021-02-09 12:53 ` Wainer dos Santos Moschetta [this message]
2021-02-09 13:29 ` Philippe Mathieu-Daudé
2021-02-09 13:41 ` Peter Maydell
2021-02-09 14:12 ` Philippe Mathieu-Daudé
2021-02-09 14:16 ` Thomas Huth
2021-02-09 14:23 ` Daniel P. Berrangé
2021-02-09 14:21 ` Daniel P. Berrangé
2021-02-09 18:09 ` Alex Bennée
2021-02-11 10:28 ` Alex Bennée
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=ebdddd92-cb51-e8b9-dfc0-fbce35015eb3@redhat.com \
--to=wainersm@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--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).