From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>, qemu-devel@nongnu.org
Cc: "Fam Zheng" <fam@euphon.net>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH v2] travis-ci: Disable C++ on Aarch64 container
Date: Mon, 8 Feb 2021 06:54:35 +0100 [thread overview]
Message-ID: <29f38036-9acd-abf4-1a75-5a4ac54273a6@redhat.com> (raw)
In-Reply-To: <20210206200537.2249362-1-f4bug@amsat.org>
On 06/02/2021 21.05, Philippe Mathieu-Daudé wrote:
> Travis-CI seems to have enforced memory limit on containers,
> and the 'GCC check-tcg' job started to fail [*]:
>
> [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.
If disabling C++ "fixes" the issue, ok ...
Otherwise, we should maybe rather limit the amount of parallel jobs there
instead? (i.e. compiling with "make -j1" in the worst case?)
Thomas
next prev parent reply other threads:[~2021-02-08 6:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-06 20:05 [PATCH v2] travis-ci: Disable C++ on Aarch64 container Philippe Mathieu-Daudé
2021-02-08 5:54 ` Thomas Huth [this message]
2021-02-08 9:16 ` Philippe Mathieu-Daudé
2021-02-08 10:09 ` Thomas Huth
2021-02-08 10:20 ` Philippe Mathieu-Daudé
2021-02-08 15:41 ` Daniel P. Berrangé
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=29f38036-9acd-abf4-1a75-5a4ac54273a6@redhat.com \
--to=thuth@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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.