#72 compile errors under Cadence Incisive with UVM report mock

[Marcin Rodzik]

I can see compilation errors while trying to use SV Unit under Incisive (I don't think the simulator matters, though). UVM report mock API seems to be imported automatically, I don't think I use it explicitly. I've made a local fix in file bin\create_testrunner.pl (see the attachment, my modification is on the left) and it helps, so I thought you might want to include this fix into SV Unit.

I was experiencing this problem a few SV Unit versions ago, figured out how to fix it, and then I was too lazy to file the ticket.

[Marcin Rodzik]

I don't use UVM Report Mock API, but I do use UVM in my unit tests (because I want to test my UVM classes). It seems usage of UVM is the trigger of the error.

[Neil Johnson]

thanks marcin. can you send me the command line and the compile error from the run.log? the report mock macro shouldn't be used the way you have it so I'm guessing I have something confusing in the documentation where I've told you something wrong elsewhere :(

[Marcin Rodzik]

Command line:

runSVUnit -u -s ius -c_arg "-incdir ../../some_other_package/sv +UVM_VERBOSITY=UVM_DEBUG -define SVUNIT_VERBOSE"

Compile errors:

import svunit_uvm_mock_pkg::svunit_uvm_test_inst;
|
ncvlog: E,NOPBIND (.testrunner.sv,8|27): Package svunit_uvm_mock_pkg could not be bound.
import svunit_uvm_mock_pkg::uvm_report_mock;
|
ncvlog: E,NOPBIND (.testrunner.sv,9|27): Package svunit_uvm_mock_pkg could not be bound.

And 'SVUNIT_VERBOSE' is just a define I'm using in my tests, it shouldn't bother you.

[Laurent Martin-Borret]

Hi Neil,
I second Marcin : I face the exact same issue (with 3.7 & 3.8) and the fix proposed works for me.
Do you think you could integrate it in next 3.9 release ?
Cheers,
Laurent