First thanks to micah, the missing package did indeed result in a working kernel compilation (gcc-5.2.1, kernel 4.1.4,grsecurity-3.1-4.1.4-201508032312.patch).
It seems I did just anything except building a new kernel.
Second, since I asked PAX team for advice, perhaps this helps somewhat
- Code: Select all
$ bash -x ./scripts/gcc-plugin.sh g++ g++ gcc
++ dirname ./scripts/gcc-plugin.sh
+ srctree=./scripts
++ gcc -print-file-name=plugin
+ gccplugins_dir=/usr/lib/gcc/x86_64-linux-gnu/5/plugin
++ g++ -E -x c++ - -o /dev/null -I./scripts/../tools/gcc -I/usr/lib/gcc/x86_64-linux-gnu/5/plugin/include
+ plugincc='<stdin>:3:2: warning: #warning g++ CXX [-Wcpp]'
+ '[' 0 -ne 0 ']'
+ case "$plugincc" in
++ g++ -c -x c++ -std=gnu++98 - -fsyntax-only -I./scripts/../tools/gcc -I/usr/lib/gcc/x86_64-linux-gnu/5/plugin/include
+ plugincc=
+ '[' 0 -eq 0 ']'
+ echo g++
g++
+ exit 0
$ bash -x ./scripts/gcc-plugin.sh
++ dirname ./scripts/gcc-plugin.sh
+ srctree=./scripts
++ -print-file-name=plugin
./scripts/gcc-plugin.sh: line 3: -print-file-name=plugin: command not found
+ gccplugins_dir=
++ -E -x c++ - -o /dev/null -I./scripts/../tools/gcc -I/include
+ plugincc='./scripts/gcc-plugin.sh: line 12: -E: command not found'
+ '[' 127 -ne 0 ']'
+ exit 1
Sorry for not understanding the solution you (both) provided sooner.
Thanks again for your efforts.