"libgmock.so" does not exist when build tvm inside vitis-ai-tensorflow container with conda vitis-ai-tensorflow env

Troubleshooting
#1

Host machine: Linux C001886040 5.11.0-43-generic #47~20.04.2-Ubuntu SMP Mon Dec 13 11:06:56 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux cuda 11.5 cmake 3.20.2 g++ (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0 gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0

demo_vitis_ai container: Linux C001886040 5.11.0-43-generic #47~20.04.2-Ubuntu SMP Mon Dec 13 11:06:56 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux cmake version 3.22.1 g++ (Ubuntu 9.4.0-1ubuntu1~18.04) 9.4.0 gcc (Ubuntu 9.4.0-1ubuntu1~18.04) 9.4.0

I am following this thread,by running :

docker run --workdir /home/jasoncat/CAT/tvm --rm --pid=host --net=host --interactive --tty --env CI_BUILD_HOME=/home/jasoncat/CAT/tvm --env CI_BUILD_USER=jasoncat --env CI_BUILD_UID=1000 --env CI_BUILD_GROUP=jasoncat --env CI_BUILD_GID=1000 --env CI_PYTEST_ADD_OPTIONS= --env CI_IMAGE_NAME=tvm.demo_vitis_ai --volume /home/jasoncat/CAT/tvm:/home/jasoncat/CAT/tvm --volume /home/jasoncat/CAT/tvm/docker:/docker --volume /dev/shm:/dev/shm --volume /opt/xilinx/dsa:/opt/xilinx/dsa --volume /opt/xilinx/overlaybins:/opt/xilinx/overlaybins tvm.demo_vitis_ai

I was able to get inside the container.

then build TVM with conda activate vitis-ai-tensorflow

mkdir build
cp cmake/config.cmake build
cd build
echo set\(USE_LLVM ON\) >> config.cmake
echo set\(USE_VITIS_AI ON\) >> config.cmake
cmake ..

however…, seems like some file was missing

Screenshot from 2021-12-18 16-39-19
Screenshot from 2021-12-18 16-39-19915×576 68.9 KB

error log file uploaded to github issue request

I have tried with conda tensorflow2 env as well, but the reason stil because of the above mentioned file missing leading to cmake test cannot perform. Thanks !

#2

There seems to be an issue in finding GTest cmake package. The temporary workaround that I followed is to edit config.cmake file https://github.com/apache/tvm/blob/92eeef6ddde9b113fd8263f1fc20f08c1c3fea0d/cmake/config.cmake#L359

ORIGINAL: set(USE_GTEST AUTO) UPDATE: set(USE_GTEST OFF)

It would be helpful if someone could confirm that this workaround might not affect any build process by any chance.

1 Like