Summary: | hardened-sources-3.8.0: doesn't build with hardened GCC due to Plugin Support missing on arm | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Delete ME <alphaomicron> |
Component: | Hardened | Assignee: | The Gentoo Linux Hardened Kernel Team (OBSOLETE) <hardened-kernel+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alexander, h.v.bruinehsen, pageexec, spender |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | ARM | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
kernel-3.8.config.vanilla
kernel-3.8.config.hardened |
Description
Delete ME
2013-03-04 23:47:05 UTC
Created attachment 340980 [details]
kernel-3.8.config.vanilla
Created attachment 340982 [details]
kernel-3.8.config.hardened
wow! This is brave :) I don't know why plugin support would fail on arm while the equivalent in amd64 or x86 is fine. Is it possible that arm gcc doesn't have plugin support yet? (In reply to comment #3) > Is it possible that arm gcc doesn't have plugin support yet? the PaX gcc plugins work fine on arm (i test them with a cross compiler) but there's indeed a problem with the gcc plugin headers installation in that on arm (or maybe just on a cross compiler) a few needed files don't get installed and one has to manually copy them from the gcc source tree to the installed plugin headers. this is not a gentoo specific problem, it happens with upstream as well. i guess one of these days i'll have to open a bug about this, in the meantime either disable the gcc plugins in PaX or keep compiling a plugin by hand and you'll see the missing includes that you can then copy from the gcc source tree. I hit the same problem with gcc 4.6.3 and 4.7.2 on the Raspberry Pi (armv6 hardfloat). Following pipacs suggestions I've copied the missing files, which turned out to be arm-cores.def and vxworks-dummy.h from the gcc source and now the kernel is compiling... :) I can also confirm that copying these two files fixes the issue. It also seems to be fixed upstream in gcc 4.8.x Further reference is for example found here: http://gcc.gnu.org/ml/gcc-patches/2013-03/msg00225.html Looks like this is fixed. |