Raphael Hertzog wrote: > A shame that your patch apply neither on the sid branch nor on the master > one. :-)
Here you go. Patch is against the sid branch. -- >8 -- Subject: dpkg-buildflags(1): -D_FORTIFY_SOURCE=2 goes in CPPFLAGS In 1.16.1.1~8 (2011-10-02), dpkg-buildflags learned to set -D_FORTIFY_SOURCE=2 in CPPFLAGS instead of CFLAGS and CXXFLAGS but the documentation wasn't updated to match. Reported-by: James Vega <[email protected]> Signed-off-by: Jonathan Nieder <[email protected]> Closes: #646073 --- debian/changelog | 6 ++++++ man/dpkg-buildflags.1 | 2 +- 2 files changed, 7 insertions(+), 1 deletions(-) diff --git a/debian/changelog b/debian/changelog index 7766c682..c70986b5 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,7 +1,13 @@ dpkg (1.16.1.2) UNRELEASED; urgency=low + [ Raphaël Hertzog ] * Fix another typo to correctly set DEB_*_ARCH_BITS in architecture.mk. + [ Jonathan Nieder ] + * Update dpkg-buildflags(1) to note that the processor option + -D_FORTIFY_SOURCE=2 is set in CPPFLAGS now instead of CFLAGS and + CXXFLAGS. Closes: #646073 + -- Raphaël Hertzog <[email protected]> Sat, 15 Oct 2011 10:49:21 +0200 dpkg (1.16.1.1) unstable; urgency=low diff --git a/man/dpkg-buildflags.1 b/man/dpkg-buildflags.1 index ba296af8..a018edba 100644 --- a/man/dpkg-buildflags.1 +++ b/man/dpkg-buildflags.1 @@ -200,7 +200,7 @@ input and contains "%n". .B fortify This setting (enabled by default) adds .B \-D_FORTIFY_SOURCE=2 -to \fBCFLAGS\fP and \fBCXXFLAGS\fP. During code generation the compiler +to \fBCPPFLAGS\fP. During code generation the compiler knows a great deal of information about buffer sizes (where possible), and attempts to replace insecure unlimited length buffer function calls with length-limited ones. This is especially useful for old, crufty code. -- 1.7.7 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
