Excerpts from build-wrapper.log
Sun Jun 28 16:59:44 2020: executable: </opt/build-wrapper-linux-x86/build-wrapper-linux-x86-64>
Sun Jun 28 16:59:44 2020: argv[0]:
Sun Jun 28 16:59:44 2020: argv[1]: <-c>
Sun Jun 28 16:59:44 2020: argv[2]: <>
Sun Jun 28 16:59:44 2020: argv[3]:
Sun Jun 28 16:59:44 2020: argv[4]:
Sun Jun 28 16:59:44 2020: argv[5]:
Sun Jun 28 16:59:44 2020: skipping process with pid: 24904
Sun Jun 28 17:00:10 2020: finalizing json file
Sun Jun 28 17:00:10 2020: returned with code: 2
I have checked settings, permissions. My trial license will expire soon and need to ensure I can get this working and desired results are achieved before we purchase.
Hello @binie,
First, you only have to call build-wrapper once with the build command instead of 3 times.
Second, sudo shouldn’t be passed to build-wrapper.
So following the build commands that you provided it should be something like that:
sudo ./autogen.sh
mkdir build
cd build
sudo ../configure
sudo build-wrapper-linux-x86-64 --out-dir /opt/builddir make clean all
sudo make check
If this still fails please can you upload the full build-wrapper log file directly after executing these commands?
many thanks @Abbas. The build-wrapper file gets created but is still empty.
I do notice that one of the functional test fails when I do a make check. Will this affect data being written to build-wrapper. I am trying to get the developers to look at this. build-wrapperlog.txt (4.6 KB)
in addition, the following command comes back with an unknown command -
sudo build-wrapper-linux-x86-64 --out-dir /opt/builddir make clean all
I have to run it as
build-wrapper-linux-x86-64 --out-dir /opt/builddir sudo make clean all
@binie,
you cannot pass sudo to build-wrapper. Do you really need sudo to build your project?
try build-wrapper-linux-x86-64 --out-dir /opt/builddir make clean all
@Abbas Thanks for all your help; I was able to get this to scan same code on ubuntu 18.04 and 20.04. We’ll move on to the next phase of getting justification