From: Jan Beulich <jbeulich@suse.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Doug Goldstein <cardoe@cardoe.com>,
Ian Jackson <iwj@xenproject.org>,
roger.pau@citrix.com, Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: [PATCH for-4.15] automation: Fix the Alpine clang builds to use clang
Date: Mon, 1 Mar 2021 09:58:48 +0100 [thread overview]
Message-ID: <c08d68a5-3c32-c6f4-dcc4-6fac29795b27@suse.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2102261446490.3234@sstabellini-ThinkPad-T480s>
On 26.02.2021 23:48, Stefano Stabellini wrote:
> On Fri, 26 Feb 2021, Andrew Cooper wrote:
>> Looks like a copy&paste error.
>>
>> Fixes: f6e1d8515d7 ("automation: add alpine linux x86 build jobs")
>> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
>
> Thanks for the patch and of course it is correct
>
> Acked-by: Stefano Stabellini <sstabellini@kernel.org>
>
>
> However unfortunately it breaks the Alpine Linux gitlab-ci again :-(
> I created a branch with Roger's patches plus this patch. The two clang
> Alpine Linux build jobs fail:
>
> https://gitlab.com/xen-project/people/sstabellini/xen/-/jobs/1059686530
> https://gitlab.com/xen-project/people/sstabellini/xen/-/jobs/1059686532
>
>
> The error is the following:
>
> <built-in>:3:10: fatal error: 'cstring' file not found
> #include "cstring"
> ^~~~~~~~~
> 1 error generated.
> make[10]: *** [Makefile:120: headers++.chk] Error 1
> make[10]: *** Waiting for unfinished jobs....
Doesn't this suggest there's a C++ compiler installed without
the headers also being available? The headers++.chk rule
requires neither or both to be present.
Jan
next prev parent reply other threads:[~2021-03-01 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 11:02 [PATCH for-4.15] automation: Fix the Alpine clang builds to use clang Andrew Cooper
2021-02-26 22:48 ` Stefano Stabellini
2021-03-01 8:58 ` Jan Beulich [this message]
2021-03-01 9:31 ` Roger Pau Monné
2021-03-06 9:24 ` Roger Pau Monné
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=c08d68a5-3c32-c6f4-dcc4-6fac29795b27@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.com \
--cc=iwj@xenproject.org \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).