lowRISC / lowRISC/ibex

having issue with PKG_CONFIG_PATH

Open
#2,263 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Type:Question
Dominant language
SystemVerilog
Stars
2.1k
Forks
810
Avg merge
5d 23h
Merged PRs (30d)
9

Description

Hi team,
This chandra tried running end-to end co simulation with lowrisc_ibex core and i am facing an issue as mentioned below,kindly help me out ,even i tried same with pre-compiled built having same issue.

make --keep-going IBEX_CONFIG=opentitan SIMULATOR=questa ISS=spike ITERATIONS=1 SEED=1 TEST=$TEST_NAME WAVES=0 COV=0
Build metadata already exists, not recreating from scratch.
Building RTL testbench
Traceback (most recent call last):
File "/home/gonu.sekhar/Desktop/ibex/dv/uvm/core_ibex/scripts/compile_tb.py", line 94, in _main
subprocess.check_output(['pkg-config', '--exists'] + spike_iss_pc)
File "/usr/lib64/python3.9/subprocess.py", line 424, in check_output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib64/python3.9/subprocess.py", line 528, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['pkg-config', '--exists', 'riscv-riscv', 'riscv-disasm', 'riscv-fdt', 'riscv-fesvr']' returned non-zero exit status 1.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/home/gonu.sekhar/Desktop/ibex/dv/uvm/core_ibex/scripts/compile_tb.py", line 149, in
sys.exit(_main())
File "/home/gonu.sekhar/Desktop/ibex/dv/uvm/core_ibex/scripts/compile_tb.py", line 96, in _main
raise RuntimeError(
RuntimeError: Failed to find ['riscv-riscv', 'riscv-disasm', 'riscv-fdt', 'riscv-fesvr'] pkg-config packages. Did you set the PKG_CONFIG_PATH correctly?
make[1]: *** [scripts/ibex_sim.mk:42: out/metadata/tb.compile.stamp] Error 1
Building randomized test generator
make[1]: *** [scripts/riscvdv.mk:61: out/metadata/instr.gen.build.stamp] Error 1
make[1]: Target 'all' not remade because of errors.
make: *** [Makefile:72: run] Error 2

## My Environment
i have followed all the steps which are mentioned in the git repo to install spike and gnu-toolchain

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with dv/uvm/core_ibex/scripts/compile_tb.py at the pkg-config check, then rerun the reported make command to inspect whether the Spike packages are discoverable. Done means the required riscv-riscv, riscv-disasm, riscv-fdt, and riscv-fesvr packages are found and the testbench build proceeds.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, python
Domain
build-system, testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.