New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't locate object method "new_cell" via package "Verilog::Netlist::Interface" #87
Comments
Original Redmine Comment I thought I had fixed this as I saw it and fixed it with the test case in your other issue. Are you using the fixed git version? |
Original Redmine Comment No I'm not. I had not used git before, and for some reason I can't check out the project from the repository.
Is there any other way to get the latest working version without using git? Thanks |
Original Redmine Comment I's worth trying to get git working, as the patch is large and given you found two issues more are possible. First, my version of git doesn't like paths in the second argument (ie use Verilog-Perl not temp/Verilog-Perl/) but I think you're beyond that. Perhaps you're at work, and need a proxy? Ask your IT person. Or look in Firefox (for example) for the settings - you can see them in Options->Advanced->Network->Settings Then export http_proxy=http://:@<proxy_ip>:<proxy_port> where: username = your network username (someuser) the full string would look like this: export http_proxy=http://someuser:somepassword@192.168.1.1:80 |
Original Redmine Comment Thanks, I've downloaded the git HEAD version. Is there a way other than editing the Makefile manually to specify a different install dir? (like the makepl_arg configuration parameter for CPAN installation)? Thanks |
Original Redmine Comment Nevermind, it seems Thanks. |
Original Redmine Comment Ok, I'm using the latest git version, and I'm still getting the same error. Can't locate object method "new_cell" via package "Verilog::Netlist::Interface" at /home/darditti/lib/perl5/x86_64-linux/Verilog/Netlist/File.pm line 238, line 94. Any ideas? Thanks, |
Original Redmine Comment Hmm, guess it's a different case from the other I fixed, sorry thought that would do it. I suspect there's something in the interface declaration that's confusing it, can you send it along? |
Original Redmine Comment I've isolated the issue, no testcase though I think its simple enough. The problem is caused by interfaces receiving other interfaces on their port-list. e.g:
This is exactly what I've got, a second interface receiving a first interface on it's port-list specifying the modport (intf1.intf2_mp). If I'm not mistaken, according to 1800-2005 Std (section A - Formal Syntax) this is allowed, as I understand the interface port-list has the same restrictions as the module port-list. Thanks again, |
Original Redmine Comment Didn't know that was possible; yes I can make a test case easily. I'll fix it. |
Original Redmine Comment Thanks a lot. |
Original Redmine Comment This is fixed in the GIT version and will be in the next release. BTW if you'd like to share your last name, I'll give you proper credit in the Changes. |
Original Redmine Comment In 3.210 |
Author Name: David A
Original Redmine Issue: 87 from https://www.veripool.org
Original Date: 2009-05-12
Original Assignee: Wilson Snyder (@wsnyder)
Hi, I have a problem with vhier, I havent prepared a testcase to upload yet, lets hope the testcase is not necessary.
I'm using vhier to generate the hierachy of a SystemVerilog small design. The top level module receives (in its port-list) several signals as well as several interfaces (system verilog interface). So I'm including (`include) all the interface definition files at the top of the file that contains the top level module (so that the "datatypes" of the interfaces are known by the parser once it reaches the port-list of the top level module).
vhier generates the following error:
Can't locate object method "new_cell" via package "Verilog::Netlist::Interface" at /usr/lib/perl5/x86_64-linux-thread-multi/Verilog/Netlist/File.pm line 238, line 94.
Line 238 of File.pm actually calls new_cell, but I'm not sure what the line 94 is referring to.
Thanks,
David
The text was updated successfully, but these errors were encountered: