Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Boris Staletic
    @bstaletic
    @klement What's the output of ldd ycm_core.so? That error shouldn't be a problem since a few years ago.
    klement
    @klement
    @bstaletic
    ksekera@c984e4769eef ~/.v/b/Y/t/ycmd ((f876f207?))> ldd ycm_core.so
            linux-vdso.so.1 (0x0000ffffa48d3000)
            libpython3.8.so.1.0 => /lib/aarch64-linux-gnu/libpython3.8.so.1.0 (0x0000ffffa3c96000)
            librt.so.1 => /lib/aarch64-linux-gnu/librt.so.1 (0x0000ffffa3c7e000)
            libstdc++.so.6 => /lib/aarch64-linux-gnu/libstdc++.so.6 (0x0000ffffa3a9b000)
            libm.so.6 => /lib/aarch64-linux-gnu/libm.so.6 (0x0000ffffa39f0000)
            libgcc_s.so.1 => /lib/aarch64-linux-gnu/libgcc_s.so.1 (0x0000ffffa39cb000)
            libc.so.6 => /lib/aarch64-linux-gnu/libc.so.6 (0x0000ffffa385a000)
            libexpat.so.1 => /lib/aarch64-linux-gnu/libexpat.so.1 (0x0000ffffa3823000)
            libz.so.1 => /lib/aarch64-linux-gnu/libz.so.1 (0x0000ffffa37f9000)
            libpthread.so.0 => /lib/aarch64-linux-gnu/libpthread.so.0 (0x0000ffffa37c9000)
            libdl.so.2 => /lib/aarch64-linux-gnu/libdl.so.2 (0x0000ffffa37b5000)
            libutil.so.1 => /lib/aarch64-linux-gnu/libutil.so.1 (0x0000ffffa37a1000)
            /lib/ld-linux-aarch64.so.1 (0x0000ffffa48a3000)
    @bstaletic this is what caught my attention
    ksekera@c984e4769eef ~/.v/b/Y/t/ycmd ((f876f207?))> less /tmp/ycmd_36547_stderr_c8lpuaa2.log
    Traceback (most recent call last):
      File "/usr/lib/python3.8/runpy.py", line 194, in _run_module_as_main
        return _run_code(code, main_globals, None,
      File "/usr/lib/python3.8/runpy.py", line 87, in _run_code
        exec(code, run_globals)
      File "/home/ksekera/.vim/bundle/YouCompleteMe/python/ycm/../../third_party/ycmd/ycmd/__main__.py", line 193, in <module>
        Main()
      File "/home/ksekera/.vim/bundle/YouCompleteMe/python/ycm/../../third_party/ycmd/ycmd/__main__.py", line 160, in Main
        code = ImportAndCheckCore()
      File "/home/ksekera/.vim/bundle/YouCompleteMe/third_party/ycmd/ycmd/utils.py", line 497, in ImportAndCheckCore
        LoadYcmCoreDependencies()
      File "/home/ksekera/.vim/bundle/YouCompleteMe/third_party/ycmd/ycmd/utils.py", line 482, in LoadYcmCoreDependencies
        ctypes.cdll.LoadLibrary( libclang_path )
      File "/usr/lib/python3.8/ctypes/__init__.py", line 451, in LoadLibrary
        return self._dlltype(name)
      File "/usr/lib/python3.8/ctypes/__init__.py", line 373, in __init__
        self._handle = _dlopen(self._name, mode)
    OSError: libtinfo.so.5: cannot open shared object file: No such file or directory
    Ben Jackson
    @puremourning
    that looks to be tring to load libclang, which means --clang-completer
    klement
    @klement
    Yes I was scared by the message so I provided both options - clang & clangd
    without clang it complained I won't have any semantic completion for c/c++/etc
    klement
    @klement
    but it seems that message is just plain wrong as it's working just fine with clangd-completer only ...
    Ben Jackson
    @puremourning
    ‘Complained’ ?
    klement
    @klement
    ah yes a better word would be warned
    ksekera@c984e4769eef ~/.v/b/YouCompleteMe (master)> ./install.py ---clangd-completer
    ...
    -- Found PythonLibs: /usr/lib/python3.8/config-3.8-aarch64-linux-gnu/libpython3.8.so (found suitable version "3.8.5", minimum required is "3.6")
    -- NOT using libclang, no semantic completion for C/C++/ObjC will be available
    -- NOT using clang-tidy for static analysis.
    ...
    so this warning is obviously not true in this case ...
    Ben Jackson
    @puremourning
    It’s kinda true. But sure you can ignore it if using clangd
    Boris Staletic
    @bstaletic
    @klement I don't know which liclang are you loading, but the one that we bundle does not depend on libtinfo.so.5.
    bstaletic@Gallifrey ycmd  (git)-[test-bench-vendoring]-% ldd third_party/clang/lib/libclang.so.11
            linux-vdso.so.1 (0x00007fff1d142000)
            libdl.so.2 => /usr/lib/libdl.so.2 (0x00007f32ef9fe000)
            libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007f32ef9dc000)
            libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007f32ef7ff000)
            libm.so.6 => /usr/lib/libm.so.6 (0x00007f32ef6b9000)
            libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007f32ef69f000)
            libc.so.6 => /usr/lib/libc.so.6 (0x00007f32ef4d6000)
            /usr/lib64/ld-linux-x86-64.so.2 (0x00007f32f5122000)
    The libclang from releases.llvm.org does depend on libtinfo.
    klement
    @klement
    Well it did some downloads, but I also have clang-11 installed system-wide. Maybe it's preferred? Eitherway ... my issue is no longer an issue, just wanted to mention it in case anybody finds the info useful
    Boris Staletic
    @bstaletic
    YCM will copy the chosen libclang to ycmd/third_party/clang/lib/libclang.so.$VERSION, so run ldd on that.
    Alvin Sun
    @alvinsunyixiao
    I am cross compiling with ARM toolchains. My project generates a compile_commands.json, but YCM seems to append more system flags.
    Printing YouCompleteMe debug information...
    -- Resolve completions: Never
    -- Client logfile: /var/folders/1t/_30c0yp97x3dt95y6wyzj26c0000gn/T/ycm_1m00i734.log
    -- Server Python interpreter: /usr/local/opt/python@3.9/bin/python3.9
    -- Server Python version: 3.9.1
    -- Server has Clang support compiled in: True
    -- Clang version: clang version 11.0.0 (https://github.com/llvm/llvm-project.git 176249bd6732a8044d457092ed932768724a6f06)
    -- Extra configuration file found and loaded
    -- Extra configuration path: /Users/alvin/iRM_Embedded_2020/.ycm_extra_conf.py
    -- C-family completer debug information:
    --   Compilation database path: None
    --   Flags: ['/Users/alvin/Downloads/gcc-arm-none-eabi-9-2020-q2-update/bin/arm-none-eabi-g++', '-x', 'c++', '-target', 'arm-none-eabi', '--driver-mode=g++', '-DARM_MATH_CM4', '-
    DEIGEN_DONT_VECTORIZE', '-DSTM32F427xx', '-DUSE_HAL_DRIVER', '-I/Users/alvin/iRM_Embedded_2020/boards/DJI_Board_TypeA/Core/Inc', '-I/Users/alvin/iRM_Embedded_2020/boards/DJI_Boar
    d_TypeA/FATFS/Target', '-I/Users/alvin/iRM_Embedded_2020/boards/DJI_Board_TypeA/FATFS/App', '-I/Users/alvin/iRM_Embedded_2020/boards/DJI_Board_TypeA/USB_DEVICE/App', '-I/Users/al
    vin/iRM_Embedded_2020/boards/DJI_Board_TypeA/USB_DEVICE/Target', '-I/Users/alvin/iRM_Embedded_2020/boards/DJI_Board_TypeA/Drivers/STM32F4xx_HAL_Driver/Inc', '-I/Users/alvin/iRM_E
    mbedded_2020/boards/DJI_Board_TypeA/Drivers/STM32F4xx_HAL_Driver/Inc/Legacy', '-I/Users/alvin/iRM_Embedded_2020/boards/DJI_Board_TypeA/Drivers/CMSIS/Include', '-I/Users/alvin/iRM
    _Embedded_2020/boards/DJI_Board_TypeA/Drivers/CMSIS/Device/ST/STM32F4xx/Include', '-I/Users/alvin/iRM_Embedded_2020/boards/DJI_Board_TypeA/DSP/Include', '-I/Users/alvin/iRM_Embed
    ded_2020/boards/DJI_Board_TypeA/Middlewares/ST/STM32_USB_Device_Library/Class/CDC/Inc', '-I/Users/alvin/iRM_Embedded_2020/boards/DJI_Board_TypeA/Middlewares/ST/STM32_USB_Device_L
    ibrary/Core/Inc', '-I/Users/alvin/iRM_Embedded_2020/boards/DJI_Board_TypeA/Middlewares/Third_Party/FatFs/src', '-I/Users/alvin/iRM_Embedded_2020/boards/DJI_Board_TypeA/Middleware
    s/Third_Party/FreeRTOS/Source/include', '-I/Users/alvin/iRM_Embedded_2020/boards/DJI_Board_TypeA/Middlewares/Third_Party/FreeRTOS/Source/CMSIS_RTOS', '-I/Users/alvin/iRM_Embedded
    _2020/boards/DJI_Board_TypeA/Middlewares/Third_Party/FreeRTOS/Source/portable/GCC/ARM_CM4F', '-I/Users/alvin/iRM_Embedded_2020/shared/bsp', '-I/Users/alvin/iRM_Embedded_2020/shar
    ed/libraries', '-I/Users/alvin/iRM_Embedded_2020/shared/third_party', '-isystem', '/Users/alvin/iRM_Embedded_2020/shared/third_party/eigen-3.3.9', '-Wall', '-Werror', '-Wextra',
    '-fdiagnostics-color=always', '-fno-exceptions', '-Og', '-g', '-DDEBUG', '-mcpu=cortex-m4', '-mthumb', '-mthumb-interwork', '-mfpu=fpv4-sp-d16', '-mfloat-abi=hard', '-ffunction-s
    ections', '-fdata-sections', '-fmessage-length=0', '-std=gnu++17', '-resource-dir=/Users/alvin/.vim/bundle/YouCompleteMe/third_party/ycmd/third_party/clang/lib/clang/11.0.0', '-i
    system', '/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1', '-isystem', '/Applications/Xcode.app/Contents/Developer/Platforms/Ma
    cOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/v1', '-isystem', '/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/local
    /include', '-isystem', '/usr/local/include', '-isystem', '/Users/alvin/.vim/bundle/YouCompleteMe/third_party/ycmd/third_party/clang/lib/clang/11.0.0/include', '-isystem', '/Appli
    cations/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include', '-isystem', '/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer
    /SDKs/MacOSX.sdk/usr/include', '-iframework', '/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks', '-iframe
    work', '/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk
    The compile commands does not include -resource-dir=xxx and everything after it. Is there a way to remove those flags?
    I tried printing the flags in my .ycm_extra_conf.py, it seems like the flags returned by Settings function does not include those system flags.
    Boris Staletic
    @bstaletic
    @alvinsunyixiao Switch to clangd and skip the extra conf.
    Johannes Wikner
    @sktt
    hey, how can tell YCM the path of my header files?
    Boris Staletic
    @bstaletic
    Do you have a compile_commands.json
    RoachZhao
    @roachsinai
    Hi, there. Does YcmCompleter GoToDefinition support open the file in current window?
    What I expected is:
    Ben Jackson
    @puremourning
    There’s an option that controls it.
    See the docs
    RoachZhao
    @roachsinai
    rightbelow YcmCompleter GoToDefinition // open in horizontal
    rightbelow vertical YcmCompleter GoToDefinition // open in vertical
    above is what I used now.

    There’s an option that controls it.

    Ok, thanks.

    Ben Jackson
    @puremourning
    I don’t think we use the mods. Maybe we should
    RoachZhao
    @roachsinai

    I don’t think we use the mods. Maybe we should

    Hi @puremourning if I set g:ycm_goto_buffer_commandto same-bufferuse rightbelow, etc will not work.

    image.png
    My current setting choseedit will run :YcmCompleter GoToDefinition
    split will run rightbelow YcmCompleter GoToDefinition
    vsplit will run rightbelow vertical YcmCompleter GoToDefinition
    wish there is a way to let edit open in current window, split in a horizontal window, and vsplit in a vertical window.
    sirius-black
    @series-black
    hi , ycm diagonation can't find qt header files
    Ben Jackson
    @puremourning
    Not sure if that’s a question or not x2
    sirius-black
    @series-black
    image.png
    image.png
    image.png
    image.png
    how can i make syntastic or ycm diagonation find the qt header files
    ?????
    Johannes Wikner
    @sktt
    @bstaletic not using compile_commands.json just entering a very basic c file with a few includes from ../include/ imported as e.g. #include <arg.h>
    thought it would be nice to just tell YCM about the include path. also about the c version
    RoachZhao
    @roachsinai

    Not sure if that’s a question or not x2

    Hi, @puremourning I've made a issue to explain my points.

    Ben Jackson
    @puremourning
    @series-black All you have to do is read the docs