Bugzilla Bug 20350

Has anyone here actually gotten iverilog to work?  It finally compiles (the 
portage version didn't for a long time) but I find it hard to believe that 
anyone has actually tested it yet.
                                                          
for 
test.v:                                                                         
                                                             
module test;                                                  
        reg abc;                                    
        initial begin
#1;
abc=1;
$display("HELLO WORLD %b",abc);
end
endmodule                                                              
traveler@bhodoo /home/traveler $ iverilog test.v              
Config file                                                   
"/var/tmp/portage/iverilog-0.7/image//usr/lib/ivl/iverilog.conf" not 
found                                                                           
                                                              
putting a symlink as /var/tmp/portage/iverilog-0.7/image linking it to / works 
but this doesn't seem like the 'proper solution.' 

I dont understand the ebuilds well enough to fix this myself...

Reproducible: Always
Steps to Reproduce:
1. emerge iverilog
2. attempt to run trivial verilog program
3. see error

Actual Results:  
the aformentioned error occurs

Expected Results:  
worked properly!

This happens because make fails with -jx where x>1. make install paths=${D}..
then 
builds stuff, setting the compile time path to the install image path.  

temporary solution:  MAKEOPTS="-j1" emerge iverilog 

Check bug 9767... 

[gorjusborg] The iverilog autoconf/automake seems to create hard references to
config files instead of using relative paths.  The executable compiles, but
when iverilog is run it complains that it cannot find the config file in the
'shadow' install directory used during the build.  The program should be
looking in the real install directory that everything gets copied to following
the compile.

Brandon, emerge calls make twice, once to build and once to install. The first
time 
PREFIX paths are /. This build fails because of -j2. Now its called a second
time 
with make path=path/to/image install. make spots that files aren't compiled, so
it 
builds them, with the hardcoded paths in. Setting MAKEOPTS="${MAKEOPTS} -j1" 
 in the ebuild would fix this problem. 

I went ahead and added a -j1 to the emake call.  Let me know if this
fixes things.

Ok, moving to TEST-REQUEST status.

db issue