| Summary: | Cannot output security warning when compiled with buildroot cross compilers | ||
|---|---|---|---|
| Product: | buildroot | Reporter: | Jason.fang <jasonvfang> |
| Component: | Other | Assignee: | unassigned |
| Status: | RESOLVED INVALID | ||
| Severity: | critical | CC: | buildroot |
| Priority: | P5 | ||
| Version: | 2013.11 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
|
Description
Jason.fang
2017-11-10 06:56:48 UTC
The warning you are looking for is supposed to be triggered by -D_FORTIFY_SOURCE=2. Fortify is a bit special: it requires support both in the compiler and in libc. GCC has this support since 4.0, but uClibc and musl don't have support for Fortify at all. Thus, there is no way that -D_FORTIFY_SOURCE=2 is going to work with uClibc. When support for Fortify will land in core Buildroot, it will depend on a glibc toolchain. See also the discussion in http://patchwork.ozlabs.org/patch/830253/ |