From: Sergey Suloev <ssuloev@orpaltech.com>
To: Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-hardening@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Linaro Toolchain Working Group
<linaro-toolchain@lists.linaro.org>,
keescook@chromium.org
Subject: Re: Compilation issue with Linaro ARM toolchain
Date: Mon, 18 Jan 2021 21:21:20 +0300 [thread overview]
Message-ID: <8ab4e82f-d2dc-a2e3-6ffe-72433419ad56@orpaltech.com> (raw)
In-Reply-To: <061303A4-51F3-42E0-BCE3-BFAF416D7609@linaro.org>
Hi, Maxim,
thank you for the reply.
Installing libmpc-dev helped.
On 18.01.2021 19:04, Maxim Kuvyrkov wrote:
>> On 18 Jan 2021, at 18:59, Mathieu Poirier <mathieu.poirier@linaro.org> wrote:
>>
>> Adding the Linaro toolchain group mailing list.
>>
>> On Mon, Jan 18, 2021 at 05:49:39PM +0300, Sergey Suloev wrote:
>>> Hi, guys,
>>>
>>> I am having an issue builduing kernel 5.11 (rc4) with Linaro ARM toolchain.
>>> The issue seems to be related to CC plugins sources.
>>> Here is my build log: https://pastebin.com/DTn7Szax. I have never seen this
>>> before with versions 5.10 and below.
> Thanks, Mathieu.
>
> Hi Sergey,
>
> MPC (along with GMP and MPFR) are libraries that GCC and its plugins depend on. I think, installing libmpc-dev or equivalent should fix the problem; installing an equivalent of “apt build-dep gcc” might be more robust.
>
> Linux kernel has recently relaxed the way it detects support for compiler plugins, so it’s now enabling them more often than before.
>
> Hope this helps,
>
> --
> Maxim Kuvyrkov
> https://www.linaro.org
>
Thanks,
Sergey
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-01-18 18:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 14:49 Compilation issue with Linaro ARM toolchain Sergey Suloev
2021-01-18 15:59 ` Mathieu Poirier
2021-01-18 16:04 ` Maxim Kuvyrkov
2021-01-18 18:21 ` Sergey Suloev [this message]
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=8ab4e82f-d2dc-a2e3-6ffe-72433419ad56@orpaltech.com \
--to=ssuloev@orpaltech.com \
--cc=keescook@chromium.org \
--cc=linaro-toolchain@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=maxim.kuvyrkov@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