Skip to content

Conversation

@daritter
Copy link
Contributor

cmakes find_path() function looks first in system directories and then
in the directories listed by PATHS. So if there are numpy includes in
/usr/include they will be found first which can break the build.

One way to fix this could be to use HINTS instead of PATHS which will be
searched before the system paths. But in this case we know which
directory we want as we got it from python so let's just skip all other
paths and just look there by adding NO_DEFAULT_PATH.

cmakes find_path() function looks first in system directories and then
in the directories listed by PATHS.  So if there are numpy includes in
/usr/include they will be found first which can break the build.

One way to fix this could be to use HINTS instead of PATHS which will be
searched before the system paths. But in this case we know which
directory we want as we got it from python so let's just skip all other
paths and just look there by adding NO_DEFAULT_PATH.
@phsft-bot
Copy link

Can one of the admins verify this patch?

@peremato
Copy link
Contributor

@phsft-bot build

@peremato peremato self-assigned this Apr 10, 2017
@phsft-bot
Copy link

Starting build on centos7/gcc49, mac1011/native, slc6/gcc49, slc6/gcc62, ubuntu14/native and CMake flags -Dccache=ON -Dimt=OFF

@peremato peremato merged commit 5d5d442 into root-project:master Apr 10, 2017
@peremato
Copy link
Contributor

Thanks very much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants