[
https://issues.apache.org/jira/browse/TS-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163503#comment-15163503
]
ASF GitHub Bot commented on TS-3938:
------------------------------------
Github user bryancall commented on the pull request:
https://github.com/apache/trafficserver/pull/497#issuecomment-188402711
@dragon512
One benefit of doing the sed at the end of the process is that the FLAGS
are in sync. Adding addition variables would require that we don't modify the
FLAGS in configure.ac after they are copied.
> Add hardening (fortify) as an option to configure
> -------------------------------------------------
>
> Key: TS-3938
> URL: https://issues.apache.org/jira/browse/TS-3938
> Project: Traffic Server
> Issue Type: New Feature
> Components: Build
> Reporter: Leif Hedstrom
> Assignee: Bryan Call
> Fix For: sometime
>
>
> It might be useful to add an option, e.g. --with-hardening, such that we can
> build with various hardening compiler options. For example. I've used
> {code}
> CC="/opt/gcc5/bin/gcc"; export CC
> CXX="/opt/gcc5/bin/g++"; export CXX
> CFLAGS="-fstack-protector -fno-omit-frame-pointer"; export CFLAGS
> CXXFLAGS="-fstack-protector -fno-omit-frame-pointer"; export CXXFLAGS
> CPPFLAGS="-D_FORTIFY_SOURCE=2"; export CPPFLAGS
> LDFLAGS="-Wl,-z,relro -Wl,-z,now"; export LDFLAGS
> "./configure" \
> "--enable-experimental-plugins" \
> "--prefix=/opt/ats" \
> "CC=/opt/gcc5/bin/gcc" \
> "CXX=/opt/gcc5/bin/g++" \
> "CFLAGS=-fstack-protector -fno-omit-frame-pointer" \
> "CXXFLAGS=-fstack-protector -fno-omit-frame-pointer" \
> "CPPFLAGS=-D_FORTIFY_SOURCE=2" \
> "LDFLAGS=-Wl,-z,relro -Wl,-z,now" \
> "$@"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
