> Here clang 3.9 works, clang 5.0 fails. Note `make clean` needed to make it > fail.
Do you build a clean clone each time? Needing `make clean` doesn't suggest so, and I personally wouldn't try rebuilding half the project with another compiler and expect things to go smoothly :) Also, just to me sure: you need to re-run configure with the new values of `CC` and `CXX`, not merely run `make CC=... CXX=...` -- the later *could* work, but it also could fail. https://travis-ci.org/geany/geany/jobs/528683476, build 1959.12: > ``` > $ export MATRIX_EVAL="CC=clang-3.5 && CXX=clang++-3.5" >$ export TRAVIS_COMPILER=gcc >$ export CXX=g++ >$ export CXX_FOR_BUILD=g++ >$ export CC=gcc >$ export CC_FOR_BUILD=gcc > ``` That's already suspicious. And the job summary suggest Travis thinks it's gcc, but we set clang-3.5. > ``` >/usr/bin/../lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8/bits/unique_ptr.h:166:18: >``` *That* gets me worried: it looks like it's using GCC 4.8 include paths with Clang… Similarly in build 1959.13 which is supposed to be Clang 5.0 : > ``` >$ export MATRIX_EVAL="CC=clang-5.0 && CXX=clang++-5.0" >$ export TRAVIS_COMPILER=clang >$ export CXX=clang++ >$ export CXX_FOR_BUILD=clang++ >$ export CC=clang >$ export CC_FOR_BUILD=clang >$ clang --version >clang version 7.0.0 (tags/RELEASE_700/final) > […] > /usr/bin/../lib/gcc/x86_64-linux-gnu/5.4.0/../../../../include/c++/5.4.0/bits/unique_ptr.h:217:18: > ``` Maybe it's nothing, but it'd get me looking. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/2067#issuecomment-490379055
