[logo] 
 
Home
News
Activity
About/Contact
Major Tools
  Dinotrace
  Verilator
  Verilog-mode
  Verilog-Perl
Other Tools
  BugVise
  CovVise
  Force-Gate-Sim
  Gspice
  IPC::Locker
  Rsvn
  SVN::S4
  SystemPerl
  Voneline
  WFH
General Info
  Papers

Issue #351

installation to non-default directory using --prefix=directory_path

Added by pekon gupta about 2 years ago. Updated about 2 years ago.

Status:Closed Start date:05/14/2011
Priority:Normal Due date:
Assignee:Wilson Snyder % Done:

0%
Category:Configure/Make/Compiling
Target version:-

Description

Hi, i observed few minor updates required in installation script. especially when installing at "non-default" directory ./configure --prefix=$VERILATOR_ROOT

1) following is directory structure created after installation $VERILATOR_ROOT -+bin -+share ---+ man ---+ verilator ------+ include ------+ bin ------+ examples

1) the 'design.mk' file created after elaboration using --exe switch .. expects "verilator.mk" (default rule file) expected path: "$VERILATOR_ROOT/include/verilator.mk" actual path: "$VERILATOR_ROOT/share/verilator/include"

2) same for "verilator_includer" expected path: "$VERILATOR_ROOT/bin" actual path: "$VERILATOR_ROOT/share/verilator/bin"

plz see if my installation was incorrect .. or something to tweak in ur "make install" script I think this happens only when you specify <non-default> $VERILATOR_ROOT using --prefix option

with regards, pekon

History

#1
Updated by Wilson Snyder about 2 years ago

  • Category set to Configure/Make/Compiling
  • Status changed from New to AskedReporter
  • Assignee set to Wilson Snyder

Can you check you're not setting VERILATOR_ROOT manually? That will override the data directory, which should be correct (with share included).

Also, what does verilator -V

print?

#2
Updated by pekon gupta about 2 years ago

Hi Wilson, Yes my mistake.. i was setting VERILATOR_ROOT variable manually. I thought like other packages, i need to set this env variable to base-directory given with '--prefix' However, after reading README, i understood that somehow verilator binaries themselves take relative path based on PATH variable.

Thanks .. this should be solved now.. u may reject this issue..

with regards, pekon

#3
Updated by Wilson Snyder about 2 years ago

  • Status changed from AskedReporter to Closed

Thanks, glad it's working.

Also available in: Atom