Systemc error when building NVDLA Test Bench about hw

[AlessandroVeronesi]

Can you share your tree.make file?
It may be that the actual SystemC path might be slightly different from what you specified in such file.

[179691368]

##=======================

Project Name Setup, multiple projects supported

##=======================
PROJECTS := nv_small

##=======================
##Linux Environment Setup
##=======================

USE_DESIGNWARE := 0
DESIGNWARE_DIR := /home/tools/synopsys/syn_2011.09/dw/sim_ver
CPP := /usr/bin/cpp
GCC := /usr/bin/gcc
CXX := /usr/bin/g++
PERL := /usr/bin/perl
JAVA := /usr/bin/java
SYSTEMC := /usr/local/systemc-2.3.0
PYTHON := /usr/bin/python3
VERDI_HOME := /usr/Synopsys/verdi/R-2020.12-SP1
NOVAS_HOME := /usr/Synopsys/verdi/R-2020.12-SP1
VCS_HOME := /usr/Synopsys/vcs/Q-2020.03-SP2-7
CLANG := /usr/bin/clang
VERILATOR := verilator ////////////////Hello, I'm having the same issue. How did you solve it?

[179691368]

Can you share your tree.make file? It may be that the actual SystemC path might be slightly different from what you specified in such file.
Hello, I'm having the same issue, my tree.make is put below by me.

[AlessandroVeronesi]

##=======================

Project Name Setup, multiple projects supported

##======================= PROJECTS := nv_small

##======================= ##Linux Environment Setup ##=======================

USE_DESIGNWARE := 0 DESIGNWARE_DIR := /home/tools/synopsys/syn_2011.09/dw/sim_ver CPP := /usr/bin/cpp GCC := /usr/bin/gcc CXX := /usr/bin/g++ PERL := /usr/bin/perl JAVA := /usr/bin/java SYSTEMC := /usr/local/systemc-2.3.0 PYTHON := /usr/bin/python3 VERDI_HOME := /usr/Synopsys/verdi/R-2020.12-SP1 NOVAS_HOME := /usr/Synopsys/verdi/R-2020.12-SP1 VCS_HOME := /usr/Synopsys/vcs/Q-2020.03-SP2-7 CLANG := /usr/bin/clang VERILATOR := verilator ////////////////Hello, I'm having the same issue. How did you solve it?

"Unfortunately", the library path seems correct.
There are two major issues I experienced when generating the environment:

1. GCC version: for newer gcc versions, there are compatibility issues as reported alreeady in #330 and #298. A proposed bugfix have been posted in #191. Unfortunately, this solved the cmod compilation, but not the testbenches compilation in my case. In case this is your issue, I would recommend you to install a legacy GCC version which produces no problem (e.g., I am working with 4.8.5).

2. Minor bug in the tmake's ready_for_test target: it happened to me that if I run tmake -build ready_for_test, it ends with an error message if I previously generate part of the outdir content through other tmake targets. Since ready_for_test already generates the vmod and the cmod too, I would suggest to clean your outdir and directly run such target.

[AlessandroVeronesi]

With respect to your comment about verilator, I cannot help since I only used Synopsys tools so far.
However, other people already reported issues when working with such tool (e.g., #334)