Moritz Muehlenhoff <[email protected]> writes: > openafs already emits dpkg-buildflags during build, but the flags are > not put into effect by the upstream buildsystem:
> | * Use dpkg-buildflags to get the default values of CFLAGS, CPPFLAGS, and > | LDFLAGS. Upstream does not entirely honor these yet, but we're > | getting closer. > I suppose that's due to src/cf/osconf.m4 overriding these flags. The trick with hardening flags in OpenAFS is that it also builds a kernel module, for which those flags are not appropriate. I assume that you're filing these bugs against any package that has had a security advisory. Note that the OpenAFS security advisory was for the kernel code, where hardening flags are a trickier issue. -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
