mac mavericks, /usr/include/module.map|36 col 14 error| header 'float.h' not found #809

marchtea · 2014-02-01T12:34:13Z

When using .ycm_extra_conf.py modified based on default version, When using :YcmDiags, I've got error.

I suppose this is a configure issue, but I have no idea how to deal with it.

Env:
Mac OSX Mavericks 10.9.1
latest clt installed

YcmDiags output:

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

DebugInfo:

Printing YouCompleteMe debug information...
-- Server has Clang support compiled in: True
-- Clang version: clang version 3.4 (tags/RELEASE_34/final)
-- Flags for /Users/summer/code/learn/monitor/src/server/monitor.cpp loaded from /Users/summer/code/learn/monitor/src/server/.ycm_extra_conf.py:
-- ['-Wall', '-Wextra', '-Wno-long-long', '-Wno-variadic-macros', '-fexceptions', '-stdlib=libc++', '-std=c++11', '-x', 'c++', '-I', '/Users/summer/code/learn/monitor/src/server/
.', '-isystem', '/usr/include', '-isystem', '/usr/local/include', '-isystem', '/Library/Developer/CommandLineTools/usr/include', '-isystem', '/Library/Developer/CommandLineTools/
usr/bin/../lib/c++/v1', '-isystem', '/Users/summer/.vim/bundle/YouCompleteMe/python/ycm/server/../../clang_includes']
-- Server running at: http://localhost:61158
-- Server process ID: 8237
-- Server logfiles:
--   /var/folders/0b/1lxv4j9d3s1d_zxtj5_9mt2m0000gn/T/ycm_temp/server_61158_stdout.log
--   /var/folders/0b/1lxv4j9d3s1d_zxtj5_9mt2m0000gn/T/ycm_temp/server_61158_stderr.log

My .ycm_extra_conf.py

import os
import ycm_core

flags = [
'-Wall',
'-Wextra',
#'-Werror',
#'-Wc++98-compat',
'-Wno-long-long',
'-Wno-variadic-macros',
'-fexceptions',
'-stdlib=libc++',
'-std=c++11',
'-x',
'c++',
'-I',
'.',
'-isystem',
'/usr/include',
'-isystem',
'/usr/local/include',
'-isystem',
'/Library/Developer/CommandLineTools/usr/include',
'-isystem',
'/Library/Developer/CommandLineTools/usr/bin/../lib/c++/v1',
]


compilation_database_folder = ''

if os.path.exists( compilation_database_folder ):
  database = ycm_core.CompilationDatabase( compilation_database_folder )
else:
  database = None

SOURCE_EXTENSIONS = [ '.cpp', '.cxx', '.cc', '.c', '.m', '.mm' ]

def DirectoryOfThisScript():
  return os.path.dirname( os.path.abspath( __file__ ) )


def MakeRelativePathsInFlagsAbsolute( flags, working_directory ):
  if not working_directory:
    return list( flags )
  new_flags = []
  make_next_absolute = False
  path_flags = [ '-isystem', '-I', '-iquote', '--sysroot=' ]
  for flag in flags:
    new_flag = flag

    if make_next_absolute:
      make_next_absolute = False
      if not flag.startswith( '/' ):
        new_flag = os.path.join( working_directory, flag )

    for path_flag in path_flags:
      if flag == path_flag:
        make_next_absolute = True
        break

      if flag.startswith( path_flag ):
        path = flag[ len( path_flag ): ]
        new_flag = path_flag + os.path.join( working_directory, path )
        break

    if new_flag:
      new_flags.append( new_flag )
  return new_flags


def IsHeaderFile( filename ):
  extension = os.path.splitext( filename )[ 1 ]
  return extension in [ '.h', '.hxx', '.hpp', '.hh' ]


def GetCompilationInfoForFile( filename ):
  # The compilation_commands.json file generated by CMake does not have entries
  # for header files. So we do our best by asking the db for flags for a
  # corresponding source file, if any. If one exists, the flags for that file
  # should be good enough.
  if IsHeaderFile( filename ):
    basename = os.path.splitext( filename )[ 0 ]
    for extension in SOURCE_EXTENSIONS:
      replacement_file = basename + extension
      if os.path.exists( replacement_file ):
        compilation_info = database.GetCompilationInfoForFile(
          replacement_file )
        if compilation_info.compiler_flags_:
          return compilation_info
    return None
  return database.GetCompilationInfoForFile( filename )


def FlagsForFile( filename, **kwargs ):
  if database:
    # Bear in mind that compilation_info.compiler_flags_ does NOT return a
    # python list, but a "list-like" StringVec object
    compilation_info = GetCompilationInfoForFile( filename )
    if not compilation_info:
      return None

    final_flags = MakeRelativePathsInFlagsAbsolute(
      compilation_info.compiler_flags_,
      compilation_info.compiler_working_dir_ )

    # NOTE: This is just for YouCompleteMe; it's highly likely that your project
    # does NOT need to remove the stdlib flag. DO NOT USE THIS IN YOUR
    # ycm_extra_conf IF YOU'RE NOT 100% SURE YOU NEED IT.
    #try:
    #  final_flags.remove( '-stdlib=libc++' )
    #except ValueError:
    #  pass
  else:
    relative_to = DirectoryOfThisScript()
    final_flags = MakeRelativePathsInFlagsAbsolute( flags, relative_to )

  return {
    'flags': final_flags,
    'do_cache': True
  }

The text was updated successfully, but these errors were encountered:

marchtea · 2014-02-01T12:48:12Z

I've already checked #303 & google, but found no solution related to this issue.

marchtea · 2014-02-01T13:14:50Z

After changing my ycm_extra_conf.py, I've got another error

/Users/summer/.vim/bundle/YouCompleteMe/python/clang_includes/module.map|1 col 8 error| redefinition of module '_Builtin_intrinsics'

Maybe it's dunplicated to #749, I'll try to reinstall again.

marchtea · 2014-02-01T14:39:17Z

solved.
Strangely, Using ./install --clang-completer generate that error, but install following instruction works well.

bryanbecker · 2014-02-12T12:51:07Z

How did you fix this? I'm getting all the errors you are, and I've reinstalled a few times.

ladislas · 2014-02-12T13:25:39Z

same here...

bryanbecker · 2014-02-12T13:32:42Z

I got it to work. You to do the long install method and not the quick one.

No need to erase your current install either. Go to the link indicated and
download the precompiled binary v 3.3 for OS X. Then just follow the
instructions as indicated (make the build directory, cd into into, run the
cmake command linking to the binary you downloaded above, then run the make
command).

On Wed, Feb 12, 2014 at 9:25 PM, Ladislas notifications@github.com wrote:

same here...

Reply to this email directly or view it on GitHubhttps://github.com//issues/809#issuecomment-34868018
.

ladislas · 2014-02-12T13:43:08Z

that's what I did twice but with the same result. Maybe Homebrew messed up stuff, I'll check later when I get the time.

bryanbecker · 2014-02-12T13:44:15Z

I also used vim & cmake from homebrew

On Wed, Feb 12, 2014 at 9:43 PM, Ladislas notifications@github.com wrote:

that's what I did twice but with the same result. Maybe Homebrew messed up
stuff, I'll check later when I get the time.

Reply to this email directly or view it on GitHubhttps://github.com//issues/809#issuecomment-34869377
.

ladislas · 2014-02-12T13:49:31Z

Me too, but I also have clang installed and after reading the comment from oblitum, I think I might have to start from scratch...

no-z-turn · 2014-02-14T17:44:20Z

Me too. I followed Full Installation Guide to install YCM. After tried several times, I found that, I have to use libclang 3.3. If I use libclang 3.4, I have the same exact errors. BTW, I use echo | clang -std=c++11 -stdlib=libc++ -v -E -x c++ - to find the correct header paths, my environment is Mavericks 10.9.1, xcode 5.0.1, brewed macvim.

marchtea · 2014-02-16T08:50:32Z

Maybe my explanation is not very clear...
I completely follow Full Installation Guide not ~~the super quick one~~ to install YCM.Other env:

clang+llvm-3.4-x86_64-apple-darwin10.9.tar.gz
brewed cmake
Mavericks 10.9.1
latest xcode command line tools
macvim download from gcode

no-z-turn · 2014-02-17T21:56:32Z

@marchtea Thanks for more details. I have exactly the same environment as yours, I followed the Full Installation Guide exactly. I tried libclang 3.4, YcmDiags gives the same errors, but everything is OK if libclang 3.3 is used. Is your .ycm_extra_conf.py same as the 1st one? I just noticed that you did not include the header path /Library/Developer/CommandLineTools/usr/bin/../lib/clang/5.0/include?

marchtea · 2014-02-18T05:10:43Z

@no-z-turn Here is my ycm_extra.conf.py

flags = [
'-Wall',
'-Wextra',
#'-Werror',
#'-Wc++98-compat',
'-Wno-long-long',
'-Wno-variadic-macros',
'-fexceptions',
'-stdlib=libc++',
# THIS IS IMPORTANT! Without a "-std=<something>" flag, clang won't know which
# language to use when compiling headers. So it will guess. Badly. So C++
# headers will be compiled as C headers. You don't want that so ALWAYS specify
# a "-std=<something>".
# For a C project, you would set this to something like 'c99' instead of
# 'c++11'.
'-std=c++11',
# ...and the same thing goes for the magic -x option which specifies the
# language that the files to be compiled are written in. This is mostly
# relevant for c++ headers.
# For a C project, you would set this to 'c' instead of 'c++'.
'-x',
'c++',
'-I',
'.',
'-isystem',
'/usr/include',
'-isystem',
'/usr/local/include',
'-isystem',
'/Library/Developer/CommandLineTools/usr/include',
'-isystem',
'/Library/Developer/CommandLineTools/usr/bin/../lib/c++/v1',
]

michaelajr · 2014-02-20T02:35:56Z

Hi - I'm having similar issues. My Location List is filled with missing header file errors from module.map. See screenshot below. Bottom pane is my conf with flags. Any ideas?

no-z-turn · 2014-02-20T17:12:58Z

@michaelajr your .ycm_extra_conf.py misses -isystem', '/usr/include', at least. you can use echo | clang -std=c++11 -stdlib=libc++ -v -E -x c++ - to figure it out.

michaelajr · 2014-02-20T17:21:24Z

@no-z-turn thanks for your reply. I added the dirs listed in the verbose output to the conf file. Still get the same problems. float.h and other headers are not found. See screen shot. Am I missing something? It works fine when I compile from the command line.

michaelajr · 2014-02-20T17:23:59Z

Screen shot of errors.

michaelajr · 2014-02-20T17:25:58Z

Prob not a huge deal. I'm doing small projects for now. Just one of those oddities that I can't figure out (which rives me crazy).

michaelajr · 2014-02-20T17:37:05Z

Also added back -std and -stdlib flags with the same result.

michaelajr · 2014-02-20T17:51:45Z

I've also verified the existence of the float header in the directory I'm using in the conf file. (I've symlinked ~/Development from ~/Dropbox/Development - but I don't think that's the issue because it did not work when I was using the System clang and the correct system folders either).

marchtea · 2014-02-21T00:44:49Z

@michaelajr
Do you install ycm using Super Quick One? My occasion is due to that. After I clean all stuff & re-clone repo, following Full installation Guide, these errors are gone.

marchtea · 2014-02-21T00:46:30Z

@michaelajr
Also, I compiled with downloaded clang not ~~the system one~~

michaelajr · 2014-02-21T00:48:38Z

@marchtea - yes, I did the full install with the system version of clang/llvm, as well as the downloaded version of clang/llvm. Same issues. Also made sure the build was using the downloaded version. Been a long day. :)

michaelajr · 2014-02-21T01:24:07Z

I'm using 10.9.1 and Xcode 5.0.2. Just can't seem to get rid of the module.map errors. Just built from scratch again, against a downloaded version of clang (3.4) and using the downloaded clang paths in the conf file - and still getting the module.map errors.

michaelajr · 2014-02-21T01:25:07Z

I'll just live with it until someone else can reproduce. Does not look like there is a ready solution. Thanks for the help.

marchtea · 2014-02-21T06:09:49Z

@michealajr
Maybe you should try clang(3.3) as @no-z-turn got the same trouble with clang 3.4.Hope it works :)

mcnulty · 2014-02-21T22:00:15Z

I was running into this error as well and reinstalling YCM did not fix it. I then reinstalled Xcode command line tools via xcode-select --install, and that appears to have fixed the problem.

oblitum · 2014-02-21T22:06:45Z

@mcnulty good point, in the past, not ycm related, when I upgraded to Mountain Lion, that was also necessary to make the system stable again, for developing.

michaelajr · 2014-02-26T18:34:25Z

So... I have not been able to fix this issue. I appreciate all the help. But I have tried all possible combinations of system clang, downloaded llvm, 3.3, 3.4, different flags and paths, etc. I can get completion. I can get error highlighting and messaging. But I can not get rid of the /usr/include/module.map errors. I reinstalled the command-line tools. I used the downloaded version of llvm both to compile YCM and in the extra conf paths in the flags, but nothing works. I'll live with it - just seems so odd. Thanks again.

oblitum · 2014-02-26T18:41:12Z

@michaelajr sad you have wasted so much time into this... by the way, I have a (very related) post about why I moved from mac, if it's an option anyway. Now I boot it in very rare situations =)

no-z-turn · 2014-03-12T15:53:50Z

@michaelajr Since xcode is upgraded to 5.1 recently. I have tried to reproduce the problem again. I used the full installation guide. Using downloaded llvm 3.4 will cause the same issue, but llvm 3.3 works fine. Using the system default clang also works fine.
Note that I did not use downloaded llvm bin files to compile ycm in any cases.

mkdir $HOME/ycm_build
cd $HOME/ycm_build
# choose one of the 3 possible cmake
cmake -G "Unix Makefiles" -DPATH_TO_LLVM_ROOT=~/ycm_temp/clang+llvm-3.3-x86_64-apple-darwin12 -DPYTHON_LIBRARY=/System/Library/Frameworks/Python.framework/Versions/2.7/Python -DPYTHON_INCLUDE_DIR=/System//Library/Frameworks/Python.framework/Versions/2.7/Headers . ~/.vim/bundle/YouCompleteMe/cpp # this is OK
or
cmake -G "Unix Makefiles" -DPATH_TO_LLVM_ROOT=~/ycm_temp/clang+llvm-3.4-x86_64-apple-darwin10.9  -DPYTHON_LIBRARY=/System/Library/Frameworks/Python.framework/Versions/2.7/Python -DPYTHON_INCLUDE_DIR=/System//Library/Frameworks/Python.framework/Versions/2.7/Headers . ~/.vim/bundle/YouCompleteMe/cpp # this one will fail
or
cmake -G "Unix Makefiles" -DUSE_SYSTEM_LIBCLANG=ON -DPYTHON_LIBRARY=/System/Library/Frameworks/Python.framework/Versions/2.7/Python -DPYTHON_INCLUDE_DIR=/System//Library/Frameworks/Python.framework/Versions/2.7/Headers . ~/.vim/bundle/YouCompleteMe/cpp # this is OK
# finally compile ycm support libs
make ycm_support_libs

YcmDiags was used to check errors.

My .ycm_extra_conf.py

flags = [
'-Wall',
'-Wextra',
# '-Werror',
# '-Wc++98-compat',
'-Wno-long-long',
'-Wno-variadic-macros',
'-fexceptions',
# '-DNDEBUG',
'-std=c++11',
# ...and the same thing goes for the magic -x option which specifies the
# language that the files to be compiled are written in. This is mostly
# relevant for c++ headers.
# For a C project, you would set this to 'c' instead of 'c++'.
'-x',
'c++',
'-I',
'.',
'-isystem',
'/usr/include',
'-isystem',
'/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include',
'-isystem',
'/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/clang/5.1/include',
'-isystem',
'/usr/local/include',
'-isystem',
'/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1',
]

nickhutchinson · 2014-03-25T22:34:27Z

So, uh, did anyone figure out what's actually going on here? Is it a libclang bug?

nickhutchinson · 2014-03-26T08:48:08Z

Okay this actually looks to be an issue with how YouCompleteMe interacts with libclang.

It appears libclang.dylib looks for the builtin compiler includes directory relative to itself at clang/3.4/include/. YCM's copy of libclang.dylib does not have this, and instead feeds libclang its own copy of the builtin headers using the compiler flag -isystem ~/.vim/bundle/YouCompleteMe/python/clang_includes or similar. This means the include search path is messed up: builtin headers now come after /usr/include and friends. In previous llvm releases this didn't matter, but as of llvm 3.4 it interacts badly with the new modules feature.

To fix this, install YCM as normal. Whether you use the install.sh or "full" guide should make no difference.

Then download LLVM 3.4, extract it somewhere and copy its lib/clang/ folder to ~/.vim/bundle/YouCompleteMe/python/ or wherever YCM is installed. Rename (or delete) the clang_includes folder that already exists there, so libclang doesn't see duplicate system headers.

Boom. No more silly module.map errors. I'll submit a proper pull request when I have time.

marchtea · 2014-03-26T17:18:06Z

@nickhutchinson Sounds fantastic. I'll try that later.

michaelajr · 2014-03-26T18:11:20Z

Can this really be?! :) Will attempt a rebuild this weekend. Thanks @nickhutchinson.

Valloric · 2014-03-26T19:52:08Z

Okay this actually looks to be an issue with how YouCompleteMe interacts with libclang.
[...]
In previous llvm releases this didn't matter, but as of llvm 3.4 it interacts badly with the new modules feature.

Thank you for taking a closer look at this and providing your analysis!

Boom. No more silly module.map errors. I'll submit a proper pull request when I have time.

Please do! If that's the actual fix I'd love to see it merged.

Valloric · 2014-04-02T22:44:11Z

PR #910 was reverted because it was breaking a lot of people; we need a more nuanced approach.

marchtea · 2014-05-04T05:10:32Z

Stuck to this problem again after update to latest YCM.

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
4 /Users/summer/.vim/bundle/YouCompleteMe/python/clang_includes/module.map|1 col 8 error| redefinition of module '_Builtin_intrinsics'

@nickhutchinson 's solution takes no effect.

/Users/summer/.vim/bundle/YouCompleteMe/python/clang/3.4/include/module.map|1 col 8 error| redefinition of module '_Builtin_intrinsics'

marchtea · 2014-05-04T05:32:57Z

then, strangely, later I install again using ./install.sh --clang-completer --system-libclang, Problem is gone.

My env is latest command line tools with llvm 3.4

Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn)
Target: x86_64-apple-darwin13.1.0
Thread model: posix
"/Library/Developer/CommandLineTools/usr/bin/clang" -cc1 -triple x86_64-apple-macosx10.9.0 -E -disable-free -disable-llvm-verifier -main-file-name - -mrelocation-model pic -pic-level 2 -mdisable-fp-elim -masm-verbose -munwind-tables -target-cpu core2 -target-linker-version 236.3 -v -resource-dir /Library/Developer/CommandLineTools/usr/bin/../lib/clang/5.1 -stdlib=libc++ -std=c++11 -fdeprecated-macro -fdebug-compilation-dir /Users/summer/code/project/advnp/monitor/src/server -ferror-limit 19 -fmessage-length 178 -stack-protector 1 -mstackrealign -fblocks -fobjc-runtime=macosx-10.9.0 -fencode-extended-block-signature -fcxx-exceptions -fexceptions -fdiagnostics-show-option -fcolor-diagnostics -vectorize-slp -o - -x c++ -
clang -cc1 version 5.1 based upon LLVM 3.4svn default target x86_64-apple-darwin13.1.0
ignoring nonexistent directory "/usr/include/c++/v1"
#include "..." search starts here:
#include <...> search starts here:
/Library/Developer/CommandLineTools/usr/bin/../lib/c++/v1
/usr/local/include
/Library/Developer/CommandLineTools/usr/bin/../lib/clang/5.1/include
/Library/Developer/CommandLineTools/usr/include
/usr/include
/System/Library/Frameworks (framework directory)
/Library/Frameworks (framework directory)
End of search list.

my flags in .ycm_extra_conf.py

flags = [
'-Wall',
'-Wextra',
#'-Werror',
#'-Wc++98-compat',
'-Wno-long-long',
'-Wno-variadic-macros',
'-fexceptions',
'-stdlib=libc++',
'-std=c++11',
'-x',
'c++',
'-I',
'.',
'-I',
'../util',
'-isystem',
'/Library/Developer/CommandLineTools/usr/bin/../lib/c++/v1',
'-isystem',
'/usr/local/include',
'-isystem',
'/Library/Developer/CommandLineTools/usr/bin/../lib/clang/5.1/include',
'-isystem',
'/Library/Developer/CommandLineTools/usr/include',
'-isystem',
'/usr/include'
]

nickhutchinson · 2014-05-04T06:53:08Z

@marchtea You've got two module.map files for the builtin headers fighting with each other; the only -isystem include path you should need to have in your .ycm_extra_conf.py is the path to the C++ headers.

unphased · 2014-08-11T21:17:01Z

I can confirm that reinstalling using ./install.sh --clang-completer --system-libclang fixed this issue for me when I encountered it today. Thanks for the tip.

wesleypeck · 2014-08-13T16:38:38Z

I resolved this successfully by following the recommendation given by @nickhutchinson except I had to copy LLVM's "lib/clang" folder to "YouCompleteMe/third_party/ycmd". In this end I had this setup:

Inside YouCompleteMe/third_party/ycmd
libclang.dylib
clang
clang/include
In .ycm_extra_conf.py
flags = ['-isystem', ''/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1']

mnloop · 2014-09-16T14:25:43Z

Again, installing using ./install.sh --clang-completer --system-libclang WITH XCODE 5.1.1 fixed this issue.

But with xcode 5.0 will cause YCM not able to launch, it required to download the latest clang version(3.4). <--- Edit: This may caused by inconsistent Python version.

Edit:
I end up using above solution from @wesleypeck,
$ ls ~/.vim/bundle/YouCompleteMe/third_party/ycmd/
libclang.dylib
clang
clang_includes

XCODE 5.1.1, llvm 3.4.2, vim 7.4.258, python 2.7.8_1

oblitum · 2014-09-28T03:52:30Z

Using OS X... Xcode and command lines tools got updated, issue started to raise.
To solve, I borrowed from @nickhutchinson approach, but avoided the extra LLVM download.

I just,

removed ycmd's clang_includes directory
mkdir clangin ycmd's directory
created simbolic link of the new system's clang includes, to the relative path expected by libclang.dylib: ln -s /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/6.0 clang/3.4

fatfatson · 2016-02-09T11:34:46Z

same problem...but osx10.11...

puremourning · 2016-02-09T14:56:36Z

You need to include OS X system header does in your flags. See the FAQ (entry contains something like clang -v -x c++ -)

On 9 Feb 2016, at 11:35, fatfatson notifications@github.com wrote:

same problem...but osx10.11...

—
Reply to this email directly or view it on GitHub.

fatfatson · 2016-02-10T11:48:56Z

@puremourning
thanks a lot~
it's ok after adding those system dir
but for android dev, i have to add ndk dir also, then it seems made conflict:

/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/cwctype|88 col 9 error| no member named 'iswblank' in the global namespace
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/cwchar|132 col 9 error| no member named 'vfwscanf' in the global namespace
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/cwchar|133 col 9 error| no member named 'vswscanf' in the global namespace
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/cwchar|134 col 9 error| no member named 'vwscanf' in the global namespace
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/cwchar|150 col 9 error| no member named 'wcstof' in the global namespace
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/cwchar|151 col 9 error| no member named 'wcstold' in the global namespace
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/cwchar|155 col 9 error| no member named 'wcstoll' in the global namespace
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/cwchar|159 col 9 error| no member named 'wcstoull' in the global namespace
/

puremourning · 2016-02-10T19:59:48Z

I'm closing this because it is not a YCM bug or feature request (per CONTRIBUTING.md).

I can't really help with your android dev question. Try asking on ycm-users.

unphased · 2016-02-17T02:40:37Z

So this problem has come back for me (Xcode 7.2.1 on 10.11) but I'll keep digging.

@oblitum your instructions sound plausible, but they are not complete. Link the .../XcodeDefault.xctoolchain/usr/lib/clang/.../3.x/ to what? In where?

Also having all these headers checked into ycmd repo sounds awful. If a clang is getting downloaded, shouldnt the download include the headers that go with the clang that got downloaded? So we should be unpacking those and referencing those, and now moving them around or changing them into a link shouldnt cause the entire repo and the parent repo to become dirty.

puremourning · 2016-02-18T00:20:00Z

You need to include the system include paths in your flags. See the FAQ about something like clang -E -x c++ -v -

marchtea closed this as completed Feb 1, 2014

marchtea mentioned this issue Feb 5, 2014

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

Closed

nickhutchinson mentioned this issue Mar 27, 2014

Fix libclang's #include search path #910

Merged

Valloric reopened this Apr 2, 2014

puremourning closed this as completed Feb 10, 2016

github-actions bot locked as resolved and limited conversation to collaborators May 31, 2021

mac mavericks, /usr/include/module.map|36 col 14 error| header 'float.h' not found #809

mac mavericks, /usr/include/module.map|36 col 14 error| header 'float.h' not found #809

Comments

marchtea commented Feb 1, 2014

marchtea commented Feb 1, 2014

marchtea commented Feb 1, 2014

marchtea commented Feb 1, 2014

bryanbecker commented Feb 12, 2014

ladislas commented Feb 12, 2014

bryanbecker commented Feb 12, 2014

ladislas commented Feb 12, 2014

bryanbecker commented Feb 12, 2014

ladislas commented Feb 12, 2014

no-z-turn commented Feb 14, 2014

marchtea commented Feb 16, 2014

no-z-turn commented Feb 17, 2014

marchtea commented Feb 18, 2014

michaelajr commented Feb 20, 2014

no-z-turn commented Feb 20, 2014

michaelajr commented Feb 20, 2014

michaelajr commented Feb 20, 2014

michaelajr commented Feb 20, 2014

michaelajr commented Feb 20, 2014

michaelajr commented Feb 20, 2014

marchtea commented Feb 21, 2014

marchtea commented Feb 21, 2014

michaelajr commented Feb 21, 2014

michaelajr commented Feb 21, 2014

michaelajr commented Feb 21, 2014

marchtea commented Feb 21, 2014

mcnulty commented Feb 21, 2014

oblitum commented Feb 21, 2014

michaelajr commented Feb 26, 2014

oblitum commented Feb 26, 2014

no-z-turn commented Mar 12, 2014

nickhutchinson commented Mar 25, 2014

nickhutchinson commented Mar 26, 2014

marchtea commented Mar 26, 2014

michaelajr commented Mar 26, 2014

Valloric commented Mar 26, 2014

Valloric commented Apr 2, 2014

marchtea commented May 4, 2014

marchtea commented May 4, 2014

nickhutchinson commented May 4, 2014

unphased commented Aug 11, 2014

wesleypeck commented Aug 13, 2014

mnloop commented Sep 16, 2014

oblitum commented Sep 28, 2014

fatfatson commented Feb 9, 2016

puremourning commented Feb 9, 2016

fatfatson commented Feb 10, 2016

puremourning commented Feb 10, 2016

unphased commented Feb 17, 2016

puremourning commented Feb 18, 2016