[
https://issues.apache.org/jira/browse/KUDU-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861755#comment-15861755
]
Matthew Jacobs commented on KUDU-1870:
--------------------------------------
I'll take a swing at this one. I was thinking that the project-config.jam could
be set from an environment variable, otherwise falling back to the default
behavior. [~dralves] [~adar] does that seem reasonable?
> Kudu thirdparty cmake build doesn't respect external compilation options
> ------------------------------------------------------------------------
>
> Key: KUDU-1870
> URL: https://issues.apache.org/jira/browse/KUDU-1870
> Project: Kudu
> Issue Type: Bug
> Components: build
> Affects Versions: 1.3.0
> Reporter: Matthew Jacobs
> Assignee: Matthew Jacobs
> Priority: Critical
> Labels: impala
>
> Impala's toolchain builds Kudu using its toolchain compiler and libraries.
> The compiler and options are set in the standard environment variables CC,
> CXX, etc., but the boost build results in the system compiler being used.
> However, the CFLAGS/CXXFLAGS do get picked up, so the combination is not
> guaranteed to be supported, and Impala toolchain builds do end up failing.
> I believe the {{project-config.jam}} needs to be set for boost to pick up the
> right compiler. It is only being set for *san builds currently (to use clang).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
