From: Paul H. Hargrove (PHHargrove_at_lbl_dot_gov)
Date: Fri Jan 16 2009 - 11:47:40 PST
Neal,
The only instance of the string "stack-protector" in the blcr-0.8.0
tarball is in the NEWS file:
$ tar xfz blcr-0.8.0.tar.gz
$ cd blcr-0.8.0/
$ find . -type f | xargs grep stack-protector
./NEWS: - Fix -fstack-protector problems w/ the .src.rpm on FC6
If you look at the output from configure step "checking for flags to
compile Linux kernel probes" you will see the flags which the kernel
Makefile uses to build modules. They are extracted by running
(approximately) "make -C ${KERNEL_SRC} builddir=<tmp>
KBUILD_EXTMOD=$(builddir)". All the resulting CFLAGS are determined by
the kernel's Makefiles, not BLCR.
So, I am 95% certain that any -fno-stack-protector you are seeing is
added by the kernel's own makefiles (not BLCR), and that rerunning
autoconf would not get rid of it either. However, I am willing to be
wrong if you can give me some idea of how to fix it.
-Paul
Neal Becker wrote:
> It looks like without running autoconf, the build of the kernel mod still uses
> -fno-stack-protector.
>
> Is it possible to get rid of this without requiring every client that builds
> the kmod to have autoconf and friends installed? This issue was brought up in
> the rpmfusion review.
>
--
Paul H. Hargrove PHHargrove_at_lbl_dot_gov
Future Technologies Group Tel: +1-510-495-2352
HPC Research Department Fax: +1-510-486-6900
Lawrence Berkeley National Laboratory