From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Roger Pau Monne <roger.pau@citrix.com>, <xen-devel@lists.xenproject.org>
Cc: Doug Goldstein <cardoe@cardoe.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Ian Jackson <iwj@xenproject.org>
Subject: Re: [PATCH for-4.15] automation/alpine: add g++ to the list of build depends
Date: Mon, 1 Mar 2021 17:59:26 +0000 [thread overview]
Message-ID: <a1d8e537-af33-3ef8-412a-6422fb4cf4ea@citrix.com> (raw)
In-Reply-To: <20210301095806.68518-1-roger.pau@citrix.com>
On 01/03/2021 09:58, Roger Pau Monne wrote:
> clang++ relies on the C++ headers installed by g++, or else a clang
> build will hit the following error:
>
> <built-in>:3:10: fatal error: 'cstring' file not found
> #include "cstring"
> ^~~~~~~~~
> 1 error generated.
> make[10]: *** [Makefile:120: headers++.chk] Error 1
>
> Reported-by: Stefano Stabellini <sstabellini@kernel.org>
> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
> ---
> Cc: Ian Jackson <iwj@xenproject.org>
> No real risk here from a release PoV, it's just pulling a package
> required for the Alpine clang build. Worse that cold happen is that
> the Alpine clang build broke, but it's already broken.
Shouldn't this be fixed upstream in Alpine? Its clearly a packaging bug.
~Andrew
next prev parent reply other threads:[~2021-03-01 17:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 9:58 [PATCH for-4.15] automation/alpine: add g++ to the list of build depends Roger Pau Monne
2021-03-01 17:20 ` Ian Jackson
2021-03-01 17:59 ` Andrew Cooper [this message]
2021-03-01 18:01 ` Andrew Cooper
2021-03-02 8:14 ` Roger Pau Monné
2021-03-02 8:53 ` Jan Beulich
2021-03-02 9:36 ` Roger Pau Monné
2021-03-02 9:54 ` Jan Beulich
2021-03-02 19:39 ` Stefano Stabellini
2021-03-06 1:40 ` Stefano Stabellini
2021-03-06 9:22 ` Roger Pau Monné
-- strict thread matches above, loose matches on Subject: below --
2021-03-01 9:57 Roger Pau Monne
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=a1d8e537-af33-3ef8-412a-6422fb4cf4ea@citrix.com \
--to=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 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.