You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (Commented) (JIRA)" <ji...@apache.org> on 2011/10/04 22:19:34 UTC
[jira] [Commented] (TS-967) Traffic Server unconditionally sets
compiler optimizing flags (with patch)
[ https://issues.apache.org/jira/browse/TS-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120435#comment-13120435 ]
Leif Hedstrom commented on TS-967:
----------------------------------
Would you mind submitting a diff against current trunk? The one here fails on most chunks.
> Traffic Server unconditionally sets compiler optimizing flags (with patch)
> --------------------------------------------------------------------------
>
> Key: TS-967
> URL: https://issues.apache.org/jira/browse/TS-967
> Project: Traffic Server
> Issue Type: Bug
> Components: Build
> Affects Versions: sometime, 3.0.1
> Reporter: Arno Toell
> Assignee: Igor Galić
> Fix For: 3.1.1
>
> Attachments: dont-unconditionally-put-in-oflags.patch
>
>
> Currently, Traffic Server unconditionally sets compiler optinizing flags, e.g. _-O3_ and ignores any setting the user might have given at build time through, e.g. {{CFLAGS}}.
> The attached patch against the current trunk checks the environment for -O flags in {{C(XX)FLAGS}} and only sets them, if the user did not define any.
> Note: I didn't test it on Solaris.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira