YcmDiags complains about /usr/lib/llvm-3.4/lib/clang/3.4/include/module.map

[dunpyl]

When running :YcmDiags on a correct C++ file, I get the following obscure error which looks like a bug:

/usr/lib/llvm-3.4/lib/clang/3.4/include/module.map|1 col 8 error| redefinition of module '_Builtin_intrinsics'

The file compiles cleanly on the exact same Clang version with clang++. This is Xubuntu 13.04 with LLVM/Clang installed from the official LLVM apt repo.

[Valloric]

You're probably not giving the right flags to clang through the ycm_extra_conf file. Pretty sure this is a duplicate of #303.

[dunpyl]

Are you sure? This warning went away for a while, then came back today as I updated YCM to latest.

It happens whether I use no ycm_extra_conf, or the one in the repo, or several cut-down variations thereof that I tried.

[dunpyl]

For what it's worth, I just recompiled from scratch exactly according to the instructions, and the error is now gone again.

Seems like something goes off during the building process. Perhaps has to do with the fact that on my first attempt I executed the build from ~/.vim/bundle/YouCompleteMe rather than in an empty directory as the instructions recommend.

[introom]

According to the tutorial, I build it with:
cd ~/.vim/bundle/YouCompleteMe
./install.sh --clang-completer
But without any success. The errors are still there:
1 /usr/include/module.map|36 col 14 error| header 'float.h' not found
2 /usr/include/module.map|81 col 14 error| header 'stdarg.h' not found
3 /usr/include/module.map|113 col 14 error| header 'tgmath.h' not found

[ladislas]

same for me but I followed the full process.

[marchtea]

@introom ,reinstall following Full Installation Guide works for me as super-quick installation generates error exactly like yours. You can check out my issue #809.

[introom]

@marchtea yes. thanks. I successfully installed it days ago (soon after you closed the #809). I comment here just to emphasize that the quick-install doesn't work.

[michaelajr]

Hi - I'm still having this issue. I've been posting to the other thread (issue 809). Are we sure this is not a bug? I think I'm configured correctly - even tried with non-system clang and I get the same thing. You can my screenshots over at issue 809.
#809

[oblitum]

I really feel these reports strange.... I'm always using YCM + clang completer from tip, from say... less than a week ago, and I never stumbled upon this issue. I'm on Ubuntu 13.10 + clang 3.5 tip of trunk + libc++ (with libc++abi since it now works on Linux, previously I was using libcxxrt to have working libc++ on Linux).

[oblitum]

by the way, I set $CC, $CXX, $CXXFLAGS and $LDFLAGS to compile YCM with clang.

[michaelajr]

@oblitum I've set $CC and $CXX. I can see when I build YCM with CMAKE that it is using these settings (which are set to the downloaded clang). Maybe I'll try this all again from scratch later tonight. Thanks!

[oblitum]

since I'm suspecting this is not an YCM issue, I googled and found some other software with the same kind of error:

pocl/pocl#53

it seems like the nature of this is having -I. in the flags?

please people, try to make sure that's not going to the YCM libclang arguments, or who knows where, both from .ycm_extra_conf and environment variables.

[oblitum]

I've seen some .ycm_extra_conf posted using that, by the way, mine doesn't have that.

[michaelajr]

@oblitum I posted my conf at #809 - I'm not using -I. Pretty sure this is a Mac thing. I'll try some more and report back.

[oblitum]

just for information on what I use for clang stuff (on Ubuntu):

export CC=clang
export CXX=clang++
export CXXFLAGS="-std=c++1y -stdlib=libc++"
export LDFLAGS="-stdlib=libc++ -lc++abi"

@michaelajr maybe. On OS X, worst even after an upgrade, I was used to that. But at last, this issue was started by someone on Xubuntu.