checkpolicy: drop -pipe compile option
The compiler option -pipe does not affect the generated code; it affects whether the compiler uses temporary files or pipes. As the benefit might vary from system to system usually its up to the packager or build framework to set it. Also these are the only places where the flag is used. Signed-off-by: Christian Göttsche <cgzones@googlemail.com>
This commit is contained in:
parent
40e2f98519
commit
02678b9d40
|
@ -10,7 +10,7 @@ TARGETS = checkpolicy checkmodule
|
|||
LEX = flex
|
||||
YACC = bison -y
|
||||
|
||||
CFLAGS ?= -g -Wall -Werror -Wshadow -O2 -pipe -fno-strict-aliasing
|
||||
CFLAGS ?= -g -Wall -Werror -Wshadow -O2 -fno-strict-aliasing
|
||||
|
||||
# If no specific libsepol.a is specified, fall back on LDFLAGS search path
|
||||
# Otherwise, as $(LIBSEPOLA) already appears in the dependencies, there
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
#
|
||||
# Makefile for building the dispol program
|
||||
#
|
||||
CFLAGS ?= -g -Wall -W -Werror -O2 -pipe
|
||||
CFLAGS ?= -g -Wall -W -Werror -O2
|
||||
|
||||
# If no specific libsepol.a is specified, fall back on LDFLAGS search path
|
||||
# Otherwise, as $(LIBSEPOLA) already appears in the dependencies, there
|
||||
|
|
Loading…
Reference in New Issue