On Fri, Jul 30, 2004 at 03:20:27PM -0400, Joshua Boyd wrote: > So, is this a native linker versus gcc problem? Are there libbz2 > dependencies I need to match up? Can I get rid of bz2 altogether? > What's it used for? Writing compressed vcd files? > > gcc -shared -o system.vpi sys_table.o sys_convert.o sys_deposit.o > sys_display.o sys_fileio.o sys_finish.o sys_plusargs.o sys_random.o > sys_readmem.o sys_readmem_lex.o sys_time.o sys_vcd.o sys_vcdoff.o > vcd_priv.o mt19937int.o priv.o stringheap.o sys_lxt.o lxt_write.o > sys_lxt2.o lxt2_write.o -L../vvp -lvpi -lbz2 -lz
OK, I went to the vpi directory and ran: gcc -shared -o system.vpi sys_table.o sys_convert.o sys_deposit.o sys_display.o sys_fileio.o sys_finish.o sys_plusargs.o sys_random.o sys_readmem.o sys_readmem_lex.o sys_time.o sys_vcd.o sys_vcdoff.o vcd_priv.o mt19937int.o priv.o stringheap.o sys_lxt.o lxt_write.o sys_lxt2.o lxt2_write.o -L../vvp -lvpi -lz Note, leaving out the -lbz2 flag. It linked without errors. I went back up a directory, and ran make && make install again. Now, I can run some of my verilog code. I wouldn't call this very thorough testing since I'm very new to verilog, but so far it appears to be working.
