| Summary: | cross-arm-none-eabi/gcc-10.1.0-r2 USE=hardened - .../work/gcc-10.1.0/libstdc++-v3/libsupc++/array_type_info.cc:30:2: sorry, unimplemented: ‘-fstack-check=specific’ for Thumb-1 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Alexandre A. Bizri <alexandre> |
| Component: | Current packages | Assignee: | Gentoo Crossdev team <crossdev> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | CC: | embedded, toolchain |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=687598 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge --info '=cross-arm-none-eabi/gcc-10.1.0-r2::crossdev'
emerge -pqv '=cross-arm-none-eabi/gcc-10.1.0-r2::crossdev' build.log of '=cross-arm-none-eabi/gcc-10.1.0-r2::crossdev' gcc-build-logs.tar.bz2 of '=cross-arm-none-eabi/gcc-10.1.0-r2::crossdev' |
||
Created attachment 649486 [details]
emerge -pqv '=cross-arm-none-eabi/gcc-10.1.0-r2::crossdev'
Created attachment 649490 [details]
build.log of '=cross-arm-none-eabi/gcc-10.1.0-r2::crossdev'
Created attachment 649492 [details]
gcc-build-logs.tar.bz2 of '=cross-arm-none-eabi/gcc-10.1.0-r2::crossdev'
Seems related to https://bugs.gentoo.org/687598 > USE: abi_x86_64 amd64 cxx elibc_glibc graphite hardened kernel_linux lto multilib nls nptl pch sanitize ssp userland_GNU vtv
Do you know where does this USE=hardened come from? It enabled stack protection by default not compatible with this particular bare-metal target.
|
Created attachment 649484 [details] emerge --info '=cross-arm-none-eabi/gcc-10.1.0-r2::crossdev' Hello all, When emerging '=cross-arm-none-eabi/gcc-10.1.0-r2::crossdev' with the 'hardened' USE flag set, I encountered a compile error of this kind: ``` sorry, unimplemented: '-fstack-check=specific' for Thumb-1 ``` With `hardened` unset (disabled) the compilation works without any hicups. Attached are - The `emerge --info` output - The `emerge -pqv` output - The `build.log` file - `gcc-build-logs.tar.bz2` as requested