None of qt5 apps wont compile with clang/llvm4 on chakra?

when I have tried to compile at least 3 different Qt5 apps (from my ccr) using clang/llvm on chakra (testing) they all have fail with damn same error : clang-4.0: error: unknown argument: '-fvar-tracking-assignments'

all my 3 pkgbuild do compile just fine on arch so it shouldn’t be a pkgbuild problem, and they do compile just fine using gcc …even more errors with clang/llvm 3.9 (on stable)

here are all the pkgbuilds : download link

PS. apparently LLVM/clang 5.0 will arrive soon

clang is much more strict as gcc and so can break some build.

well it would be nice to know why those pkgs wont compile on chakraOS and just fine on Arch…if its a pkgbuild problem or some config …or bug in some of chakra pkgs (qt5 or clang/llvm ) etc.

perhaps arch using more new/bug fixed program version?
since the ncurses group update (1.2.2017) i have massive comiling problems with some PKGBUILDs

well clang/llvm seems to be the same on both, qt5-base on arch does have 2 patches what chakra dont have. I would hope that some at chakra team would look into this before moving clang/llvm4 to stable because this is a problem

(I doubt chakra will move to llvm5 which should arrive any day now.)

I don’t think so, but it may change.

this is the Clang difference between arch and chakra (could GCC be the culprit?):

---------------ARCH---------------
[ahjolinna@arch-anywhere]: ~>$ clang -v
clang version 4.0.1 (tags/RELEASE_401/final)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-pc-linux-gnu/5.4.0
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-pc-linux-gnu/7.1.1
Found candidate GCC installation: /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/5.4.0
Found candidate GCC installation: /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/7.1.1
Found candidate GCC installation: /usr/lib/gcc/x86_64-pc-linux-gnu/5.4.0
Found candidate GCC installation: /usr/lib/gcc/x86_64-pc-linux-gnu/7.1.1
Found candidate GCC installation: /usr/lib64/gcc/x86_64-pc-linux-gnu/5.4.0
Found candidate GCC installation: /usr/lib64/gcc/x86_64-pc-linux-gnu/7.1.1
Selected GCC installation: /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/7.1.1
Candidate multilib: .;@m64
Candidate multilib: 32;@m32
Selected multilib: .;@m64
[ahjolinna@arch-anywhere]: ~>$ 


------------------ChakraOS----------------------

[ahjolinna@acer-aspire ~]$ clang -v
clang version 4.0.1 (tags/RELEASE_401/final)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-pc-linux-gnu/6.3.1
Found candidate GCC installation: /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/6.3.1
Found candidate GCC installation: /usr/lib/gcc/x86_64-pc-linux-gnu/6.3.1
Found candidate GCC installation: /usr/lib64/gcc/x86_64-pc-linux-gnu/6.3.1
Selected GCC installation: /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/6.3.1
Candidate multilib: .;@m64
Candidate multilib: 32;@m32
Selected multilib: .;@m64

have you two different versions installed?

yes, 7.1.1 (soon 7.2) is oc what arch uses as default, and as cuda8 only works with 5.x (thankfully cuda9 is arriving soon) so that’s why I have 5.4 also

This topic was automatically closed 170 days after the last reply. New replies are no longer allowed.