[
https://issues.apache.org/jira/browse/ARROW-4407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17661429#comment-17661429
]
Rok Mihevc commented on ARROW-4407:
-----------------------------------
This issue has been migrated to [issue
#20970|https://github.com/apache/arrow/issues/20970] on GitHub. Please see the
[migration documentation|https://github.com/apache/arrow/issues/14542] for
further details.
> [C++] ExternalProject_Add does not capture CC/CXX correctly
> -----------------------------------------------------------
>
> Key: ARROW-4407
> URL: https://issues.apache.org/jira/browse/ARROW-4407
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++
> Affects Versions: 0.12.0
> Reporter: Francois Saint-Jacques
> Assignee: Francois Saint-Jacques
> Priority: Minor
> Labels: pull-request-available
> Fix For: 0.13.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> The issue is that CC/CXX environment variables are captured on the first
> invocation of the builder (e.g make or ninja) instead of when CMake is
> invoked into to build directory. This can lead to compilation errors (notably
> when compiling with clang in the top directory due to the addition of the
> `-Qunused-arguments` option).
> This leads to an issue where I have a script that prepare the build directory
> and export CXX within the script. When I jump in the build folder, there's a
> mismatch between the external gbenchmark (and all deps if conda is not used)
> compiler and the build.
> To reproduce:
> # Create a new build directory with clang as compiler, don't build yet
> # In a new shell (without the compiler environment variable), go into
> directory invoke make/ninja
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
