Comment 7 for bug 1432882

This issue could be linked to this entry of the llvm libtooling FAQ:
http://clang.llvm.org/docs/LibTooling.html#libtooling-builtin-includes

Quoting:
"Clang tools need their builtin headers and search for them the same way Clang does. Thus, the default location to look for builtin headers is in a path $(dirname /path/to/tool)/../lib/clang/3.3/include relative to the tool binary. This works out-of-the-box for tools running from llvm’s toplevel binary directory after building clang-headers, or if the tool is running from the binary directory of a clang install next to the clang binary."

I guess this could explain the "../lib/clang/3.4" in libclang.

I have another machine running quantal, and on which I could install libclang1-3.3 and libclang1-3.4 from the llvm PPA (ppa:h-rayflood/llvm). Here too, the library search dirs start with the same "../lib/clang/", but these versions work perfectly. There must be something different in the way they are built, however from what I could gather this PPA is just taking the packages from Debian without modification:
http://http.debian.net/debian/pool/main/l/llvm-toolchain-3.4

I will try this approach in lucid, replacing the packages provided by Ubuntu and report back.