Change History (5)
comment:1 by , 8 years ago
comment:2 by , 8 years ago
In the Makefile in the root of the source tree:
prepare0: archprepare $(Q)$(MAKE) $(build)=. # All the preparing.. prepare: prepare0 prepare-objtool ifdef CONFIG_STACK_VALIDATION has_libelf := $(call try-run,\ echo "int main() {}" | $(HOSTCC) -xc -o /dev/null -lelf -,1,0) ifeq ($(has_libelf),1) objtool_target := tools/objtool FORCE else $(warning "Cannot use CONFIG_STACK_VALIDATION, please install libelf-dev or elfutils-libelf-devel") SKIP_STACK_VALIDATION := 1 export SKIP_STACK_VALIDATION endif endif
It seems that if CONFIG_STACK_VALIDATION is requested/set, elfutils is required (specifically libelf - probably for an interpreter during compilation)
comment:3 by , 8 years ago
OK, I looked at the help for STACK_VALIDATION
Symbol: STACK_VALIDATION │ │ Type : │ │ Prompt: Compile-time stack metadata validation |
That would be for a kernel developer. I suppose we could add a note with a reference to BLFS, but we do not need to add elfutils to LFS.
I'm really don't think that even a note is needed. After all, the STACK_VALIDATION option is at
Kernel Hacking --> Compile-time checks and compiler options --> [ ] Compile-time stack metadata validation
and is not on by default.
comment:4 by , 8 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
After thinking about it, I don't think we need to make any changes for this.
Note:
See TracTickets
for help on using tickets.
We need more information. this does not make sense. The kernel cannot use any user space files like elfutils. I just ran a check in a pristine LFS environment with no problems: