On Mon, Oct 12, 2015 at 03:46:30PM -0400, Donald Sharp wrote: > In cdefs.h we have this: > > /* If fortification mode, we warn about unused results of certain > function calls which can lead to problems. */ > #if __GNUC_PREREQ (3,4) > # define __attribute_warn_unused_result__ \ > __attribute__ ((__warn_unused_result__)) > # if __USE_FORTIFY_LEVEL > 0 > # define __wur __attribute_warn_unused_result__ > # endif
I believe Debian uses __USE_FORTIFY_LEVEL automatically these days. Other distributions might not. $ dpkg-buildflags CFLAGS=-g -O2 -fstack-protector-strong -Wformat -Werror=format-security CPPFLAGS=-D_FORTIFY_SOURCE=2 CXXFLAGS=-g -O2 -fstack-protector-strong -Wformat -Werror=format-security FCFLAGS=-g -O2 -fstack-protector-strong FFLAGS=-g -O2 -fstack-protector-strong GCJFLAGS=-g -O2 -fstack-protector-strong LDFLAGS=-Wl,-z,relro OBJCFLAGS=-g -O2 -fstack-protector-strong -Wformat -Werror=format-security OBJCXXFLAGS=-g -O2 -fstack-protector-strong -Wformat -Werror=format-security So looks like the FORTIFY_SOURCE is probably the difference. Maybe the quagga package when built on fedora does not turn that on, and the debian one does. -- Len Sorensen _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
