[
https://issues.apache.org/jira/browse/TS-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644634#comment-13644634
]
James Peach commented on TS-1838:
---------------------------------
The root cause of this is that our "compiler detection" logic is really
primitive. This also manifests itself when we run the clang static analyzer.
The analyzer is detected as gcc and we proceed to pass invalid compiler options
to it.
> When using non-gcc compilers (e.g. clang) we don't support ccache build option
> ------------------------------------------------------------------------------
>
> Key: TS-1838
> URL: https://issues.apache.org/jira/browse/TS-1838
> Project: Traffic Server
> Issue Type: Bug
> Components: Build
> Reporter: Leif Hedstrom
>
> It also doesn't like e.g.
> {code}
> ./configure CC='ccache clang'
> {code}
> Because, now cc != "clang". What's worse, doing e.g.
> {code}
> ./configure CC='ccache-3.2.1'
> {code}
> probably doesn't work either. The case statement is to specific, we should
> probably wildcard it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
