lib/raid6/neon4.c:118:1: internal compiler error: in dwarf2out_frame_debug_adjust_cfa, at dwarf2cfi.c:1078

[siva93krishna]

Hi ,
I am facing Below issue while trying to cross compile kernel for RPI3.

followed below link .

https://www.raspberrypi.org/documentati ... uilding.md

Log :
[email protected]:~/rpi/linux$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- zImage modules dtbs
CHK include/config/kernel.release
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
CHK include/generated/bounds.h
CHK include/generated/timeconst.h
CHK include/generated/asm-offsets.h
CALL scripts/checksyscalls.sh
CHK scripts/mod/devicetable-offsets.h
CHK include/generated/compile.h
CHK kernel/config_data.h
CC [M] lib/raid6/neon4.o
lib/raid6/neon4.c: In function ‘raid6_neon4_gen_syndrome_real’:
lib/raid6/neon4.c:118:1: internal compiler error: in dwarf2out_frame_debug_adjust_cfa, at dwarf2cfi.c:1078
}
^
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.launchpad.net/gcc-linaro> for instructions.
scripts/Makefile.build:328: recipe for target 'lib/raid6/neon4.o' failed
make[2]: *** [lib/raid6/neon4.o] Error 1
scripts/Makefile.build:587: recipe for target 'lib/raid6' failed
make[1]: *** [lib/raid6] Error 2
Makefile:1034: recipe for target 'lib' failed

[jamesh]

What git branch are you on? Should be the 4.14.y one.

[siva93krishna]

i am in rpi-4.14.y

git branch result

* rpi-4.14.y

issue is with cross compiler.but i followed steps mentioned in below link

https://www.raspberrypi.org/documentati ... uilding.md

But i Enabled DEBUG_INFO

then i am facing that issue .

Please give me the inputs .

[jamesh]

i am in rpi-4.14.y

git branch result

* rpi-4.14.y

issue is with cross compiler.but i followed steps mentioned in below link

https://www.raspberrypi.org/documentati ... uilding.md

But i Enabled DEBUG_INFO

then i am facing that issue .

Please give me the inputs .

So it compiles cleanly if DEBUG_INFO is not enabled?

[siva93krishna]

yes . no issues if i am disabling DEBUG_INFO

kernelhacking-> Compile the kernel with debug info

[jamesh]

Do you use any other non-standard configs that might be affecting the build?

TBH, there not much we can do about this - its an internal compiler error, so would be dealt with by the GCC team, and they have probably already fixed it in more recent versions.

So you could try a different toolchain with a more recent compiler, I believe there are other third party ones out there. Or compile on the Pi itself which I think is a new compiler version, but that will be slower

[siva93krishna]

Do you use any other non-standard configs that might be affecting the build?

TBH, there not much we can do about this - its an internal compiler error, so would be dealt with by the GCC team, and they have probably already fixed it in more recent versions.

So you could try a different toolchain with a more recent compiler, I believe there are other third party ones out there. Or compile on the Pi itself which I think is a new compiler version, but that will be slower

Hi Jamesh ,
Thanks for your reply.

can you please provide links for third party toolchain.

[jamesh]

No, but I expect Google will find something. Or you could probably build the toolchain yourself.

[ppryga]

Hi there,

I have had similar problem and fortunately found some solution. In the tools repository there is newer toolchain 4.9.3. Use that and kernel including debug symbols will build successfully. I haven't try to run it on a device yet, but gdb had loaded vmlinux and symbols are there.

Greetings,
Piotr

[asavah]

What's your gcc version/toolchain?

https://github.com/raspberrypi/tools/issues/52

On a side note: that ancient crap on the tools repo should be updated to match gcc/binutils version in raspbian.