IWYU fails to compile hpp file, with error unable to handle compilation, expected exactly one compiler job in

[vikramojha89]

While trying to run IWYU on hpp file, its giving above issue "unable to handle compilation, expected exactly one compiler job in"

The problem is it copies duplicate command, In log I can see it has two path for iwyu copied twice

Below is snippet for output
"/path/iwyu/iwyu-0.16/install/glnxa64/bin/include-what-you-use" "-cc1" "-triple" "x86_64-unknown-linux-gnu" "-fsyntax-only" "-disable-free" "-disable-llvm-verifier" "-discard-value-names" "-main-file-name" "foo.hpp" "some_other_compiler_options" "c++header" "foo.cpp" ; "/path/iwyu/iwyu-0.16/install/glnxa64/bin/include-what-you-use" "-cc1" "-triple" "x86_64-unknown-linux-gnu" "-fsyntax-only" "-disable-free" "-disable-llvm-verifier" "-discard-value-names" "-main-file-name" "foo.hpp" "some_other_compiler_options" "c++header" "foo.cpp" ;

Reproduction steps

foo.hpp

`#include
#include

int prettyprint();

void foo();`

Command used

python iwyu_tool.py -j12 -o iwyu -p compile_commands.json foo.hpp

Compiler

clang -12
OS: Debian 11

Include-what-you-use

clang version 12.0.1
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir:
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/10
Selected GCC installation: /usr/lib/gcc/x86_64-linux-gnu/10
Candidate multilib: .;@m64
Candidate multilib: 32;@m32
Candidate multilib: x32;@MX32
Selected multilib: .;@m64

[kimgr]

iwyu_tool.py just reads compile_commands.json, looks up the input filename and invokes include-what-you-use with the corresponding compile command. So I suspect your compile_command.json has that double-command in it for foo.hpp. How did you generate it? The ; separator makes me think CMake?

[vikramojha89]

I tried debugging iwyu_tool.py here inside main

invocations = [ Invocation.from_compile_command(e, extra_args) for e in compilation_db ]

invocations.command returns exactly one command to execute. Same is sent to execute function, during execution somehow its not doing it right.

Just to add this runs fine if I use cpp file, instead of hpp file, I see only one iwyu executable path.

[kimgr]

Does it make any difference if you leave out -j12?

Could you show the entry from the compilation database for foo.hpp?

[vikramojha89]

Hi Kim,

Without -j option also it didn't work.

I was manually creating a compile_commands.json by fetching compiler options, filename and directory. (This works for *.cpp file)

I now used a compdb to genreate compile_commands .json for hpp file, it runs but still it doesn't give proper output

Compile_commands.json

[
{
  "directory": "exploring-cpp-modules/iwyu/build",
  "command": "/usr/bin/c++ -std=gnu++11 -o CMakeFiles/Foo.dir/foo.cxx.o -c exploring-cpp-modules/iwyu/foo.cxx",
  "file": "exploring-cpp-modules/iwyu/foo.cxx",
  "output": "CMakeFiles/Foo.dir/foo.cxx.o"
},

{
  "directory": "exploring-cpp-modules/iwyu/build",
  "command": "/usr/bin/c++ -std=gnu++11 -c exploring-cpp-modules/iwyu/foo.hpp",
  "file": "exploring-cpp-modules/iwyu/foo.hpp"
}
]

CMake

cmake_minimum_required(VERSION 3.10)

project(Foo)

set(CMAKE_CXX_STANDARD 11)
set(CMAKE_CXX_STANDARD_REQUIRED true)


add_executable(Foo foo.cxx)
target_link_libraries(Foo foo.hpp)

Source File

foo.cxx

#include "foo.hpp"

void prettyprint() {
    std::cout<<"Hello";
}

void foo() {
    std::cout<<"foo";
}

int main() {
    return 0;
}

foo.hpp

#include <vector>
#include <iostream>

void prettyprint();

void foo();

[kimgr]

it runs but still it doesn't give proper output

What does this mean? Can you show the output you get?

[vikramojha89]

ya sorry I missed the output

In file included from exploring-cpp-modules/iwyu/foo.hpp:1: In file included from /usr/lib/gcc/x86_64-linux-gnu/10/../../../../include/c++/10/vector:64: In file included from /usr/lib/gcc/x86_64-linux-gnu/10/../../../../include/c++/10/bits/allocator.h:46: In file included from /usr/lib/gcc/x86_64-linux-gnu/10/../../../../include/x86_64-linux-gnu/c++/10/bits/c++allocator.h:33: In file included from /usr/lib/gcc/x86_64-linux-gnu/10/../../../../include/c++/10/ext/new_allocator.h:33: In file included from /usr/lib/gcc/x86_64-linux-gnu/10/../../../../include/c++/10/new:41: In file included from /usr/lib/gcc/x86_64-linux-gnu/10/../../../../include/c++/10/exception:147: In file included from /usr/lib/gcc/x86_64-linux-gnu/10/../../../../include/c++/10/bits/exception_ptr.h:38: /usr/lib/gcc/x86_64-linux-gnu/10/../../../../include/c++/10/bits/cxxabi_init_exception.h:38:10: fatal error: 'stddef.h' file not found #include <stddef.h> ^~~~~~~~~~

[kimgr]

https://github.com/include-what-you-use/include-what-you-use#how-to-install

[kimgr]

This turned into a duplicate of #100. Closing.