From: Dinh Nguyen <dinguyen@kernel.org>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org, masahiroy@kernel.org
Subject: Re: commit ("1e860048c53ee gcc-plugins: simplify GCC plugin-dev capability test")
Date: Thu, 7 Jan 2021 08:45:15 -0600 [thread overview]
Message-ID: <25ae82e1-e864-807f-9ca5-f6571ef3a12b@kernel.org> (raw)
In-Reply-To: <202101061512.E0F3D28@keescook>
On 1/6/21 5:14 PM, Kees Cook wrote:
> On Wed, Jan 06, 2021 at 08:44:58AM -0600, Dinh Nguyen wrote:
>> Hi Masahiro,
>>
>> With v5.11-rc1 and commit("1e860048c53ee gcc-plugins: simplify GCC
>> plugin-dev capability test"), I get this error for my arm socfpga_defconfig
>> build. I have been building the kernel the same way for many years now. Do
>> you know what I might be doing wrong?
>>
>> $ make ARCH=arm CROSS_COMPILE=${CROSS_COMPILE}
>> SYNC include/config/auto.conf.cmd
>> SYSHDR arch/arm/include/generated/uapi/asm/unistd-common.h
>> SYSHDR arch/arm/include/generated/uapi/asm/unistd-oabi.h
>> SYSHDR arch/arm/include/generated/uapi/asm/unistd-eabi.h
>> REMOVE arch/arm/include/generated/asm/mm-arch-hooks.h
>> HOSTCXX scripts/gcc-plugins/arm_ssp_per_task_plugin.so
>> In file included from scripts/gcc-plugins/gcc-common.h:103:0,
>> from scripts/gcc-plugins/arm_ssp_per_task_plugin.c:3:
>> /home/dinguyen/linux_dev/gcc-arm-10.2-2020.11-x86_64-arm-none-linux-gnueabihf/bin/../lib/gcc/arm-none-linux-gnueabihf/10.2.1/plugin/include/builtins.h:23:10:
>> fatal error: mpc.h: No such file or directory
>> #include <mpc.h>
>> ^~~~~~~
>> compilation terminated.
>> scripts/gcc-plugins/Makefile:47: recipe for target
>> 'scripts/gcc-plugins/arm_ssp_per_task_plugin.so' failed
>> make[2]: *** [scripts/gcc-plugins/arm_ssp_per_task_plugin.so] Error 1
>> scripts/Makefile.build:496: recipe for target 'scripts/gcc-plugins' failed
>> make[1]: *** [scripts/gcc-plugins] Error 2
>> Makefile:1190: recipe for target 'scripts' failed
>> make: *** [scripts] Error 2
>> make: *** Waiting for unfinished jobs....
>> UPD include/config/kernel.release
>>
>> Thanks,
>> Dinh
>
> Hi! Thanks for the report. Other folks have also encountered this,
> and it appears to be a problem with distro packaging of the gcc plugin
> development packages. You'll need to install the GNU multiprecision
> libraries ("gmp-devel" on most rpm-based systems, "libgmp-dev" on most
> debian systems)[1].
>
> Hopefully that'll work!
>
Thanks, that worked! I also had to install libmpc-dev as well.
Dinh
prev parent reply other threads:[~2021-01-07 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 14:44 Dinh Nguyen
2021-01-06 23:14 ` Kees Cook
2021-01-07 14:45 ` Dinh Nguyen [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=25ae82e1-e864-807f-9ca5-f6571ef3a12b@kernel.org \
--to=dinguyen@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.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
all inboxes | Powered by JetHome®