Skip to content
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

verilator_includer installed to two locations #48

Closed
veripoolbot opened this issue Jan 9, 2009 · 2 comments
Closed

verilator_includer installed to two locations #48

veripoolbot opened this issue Jan 9, 2009 · 2 comments
Assignees
Labels
area: configure/compiling Issue involves configuring or compilating Verilator itself resolution: fixed Closed; fixed

Comments

@veripoolbot
Copy link
Contributor


Author Name: Lane Brooks
Original Redmine Issue: 48 from https://www.veripool.org
Original Date: 2009-01-09
Original Assignee: Wilson Snyder (@wsnyder)


The verilator_includer perl file is being installed to both /usr/bin/verilator_includer and /usr/share/verilator/bin/verilator_includer. Based on my experiments to remove either one, it seems the one in /usr/share/verilator/bin is the critical one. I am only reporting this as an issue in case you want to clean it up. For the Fedora rpm, I am deleting the one put in /usr/bin because of requests not to have duplicate files. My verilator simulations run just fine without the one in /usr/bin.

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2009-05-08T19:06:52Z


Fixed in git version.

(Part of the delay was in stomping out some differences in how I personally install it.)

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2009-05-19T14:24:51Z


In 3.710

@veripoolbot veripoolbot added area: configure/compiling Issue involves configuring or compilating Verilator itself resolution: fixed Closed; fixed labels Dec 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: configure/compiling Issue involves configuring or compilating Verilator itself resolution: fixed Closed; fixed
Projects
None yet
Development

No branches or pull requests

2 participants