Fix: force the use of our _FORTIFY_SOURCE definition
authorJonathan Rajotte <jonathan.rajotte-julien@efficios.com>
Tue, 4 Feb 2020 21:04:41 +0000 (16:04 -0500)
committerJérémie Galarneau <jeremie.galarneau@efficios.com>
Fri, 7 Feb 2020 18:34:42 +0000 (13:34 -0500)
commit016f04504bc66d2cb6b082685c85ce817c25df78
treed6a5ca641bc2d0eaec00a6ed2b59a15ded603e1f
parentbfb025cd1038e01972c11fdf5fcad8b044b03f76
Fix: force the use of our _FORTIFY_SOURCE definition

Some toolset (ubuntu) already defined the _FORTIFY_SOURCE.

This removes the warning we see if this is the case. Unset the variable and
reset it.

The warning:

make[3]: Entering directory '/home/joraj/lttng/master/lttng-tools/tests/regression/kernel'
  CC       select_poll_epoll-select_poll_epoll.o
<command-line>: warning: "_FORTIFY_SOURCE" redefined
<built-in>: note: this is the location of the previous definition
  CCLD     select_poll_epoll

Signed-off-by: Jonathan Rajotte <jonathan.rajotte-julien@efficios.com>
Change-Id: I2fa0482afa8941705a992f62a2e63657ea9e2b87
Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
tests/regression/kernel/Makefile.am
This page took 0.025959 seconds and 4 git commands to generate.