(sorry, I meant of course "trusty", not "lucid", in the above post)

I confirm that the libclang from the above PPA (1:3.4.2-debian13trusty1)
does work correctly in trusty. In other words, when I compile the
example programs attached to this bug report with the libclang from this
PPA, the errors about ia32intrin.h are gone and parsing is fully
functional. I don't know if this is due to 1) a more recent upstream
libclang version (3.4.2 vs 3.4), 2) a more recent debian base, or 3)
tweaks specific to this PPA.

If someone familiar with the debian/ubuntu build system could take a look at 
the source of this PPA:
https://github.com/hATrayflood/llvm-ppa

... and compare to what is done for the official ubuntu packages, that would be 
great. I have tried myself, but the thing is so complex and globally unknown to 
me that I am completely lost. From what I could gather, it seems that the 
maintainer of the PPA actually has made a few modifications to the original 
debian packages, as can be seen from this diff file:
https://github.com/hATrayflood/llvm-ppa/blob/master/trusty/llvm-toolchain-3.4/debian.diff

Also, can someone else actually reproduce this issue on their side?

NB: Using the PPA libclang, the builtin search directories are similar to the 
original ubuntu version. So that lead was a dead end. Here is the output of 
-print-search-dirs:
programs: =:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../x86_64-linux-gnu/bin
libraries: 
=../lib/clang/3.4.2:/usr/lib/gcc/x86_64-linux-gnu/4.8:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib/../lib64:/usr/lib/x86_64-linux-gnu:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../..:/lib:/usr/lib

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1432882

Title:
  libclang1 has wrong standard include paths

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1432882/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to