aboutsummaryrefslogtreecommitdiff
path: root/shlib-versions
diff options
context:
space:
mode:
authorDmitry V. Levin <ldv@altlinux.org>2012-08-23 14:29:43 +0000
committerDmitry V. Levin <ldv@altlinux.org>2012-10-02 19:22:57 +0000
commitfc997c6e55cc2636681db298eac4cb7c8568708f (patch)
tree72007f9f2ca467a15236b0ee4ba1ca9160e1c7cd /shlib-versions
parentbb9510dc345f0b24de212604b2308dc6e6cc939a (diff)
downloadglibc-fc997c6e55cc2636681db298eac4cb7c8568708f.tar
glibc-fc997c6e55cc2636681db298eac4cb7c8568708f.tar.gz
glibc-fc997c6e55cc2636681db298eac4cb7c8568708f.tar.bz2
glibc-fc997c6e55cc2636681db298eac4cb7c8568708f.zip
nscd: fix compilation flags
Commit 61653dfb81b776bb72ce4304175b861d77c357a8 added support for compilers predefining _FORTIFY_SOURCE by adding -U_FORTIFY_SOURCE to CPPFLAGS for these compilers, but that change doesn't work quite well in case of nscd: its Makefile sets _FORTIFY_SOURCE using CFLAGS instead of CPPFLAGS and, thanks to compilation rules defined in Makerules, CPPFLAGS are passed to compiler after CFLAGS, resulting to a build with _FORTIFY_SOURCE turned off. This change implements a more safe method of passing preprocessor and compiler flags so that no nscd modules could be accidentally forgotten.
Diffstat (limited to 'shlib-versions')
0 files changed, 0 insertions, 0 deletions