-
Notifications
You must be signed in to change notification settings - Fork 267
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
A workaround for a bug in the Modelsim vmap command on some Linux hosts #80
Comments
Maybe it modifies some other modelsim.ini? We use I have made a possible fix in the issue_80 branch were I change the current working directory before calling |
I don't know exactly what the problem is, but it occurs in our own scripts even though we do not use the |
I've tried the new branch. Unfortunately it did not help. I tried to find out if any other modelsim.ini had been edited, but there is only one other modelsim.ini in our case. It resides in ./opt/altera/14.0/modelsim_ase/modelsim.ini, and it had not been edited. As I mentioned this happens when we call vmap with our own scripts as well, so it's not a problem with vUnit itself. But it would be nice if we didn't have to think about it! |
Is it bug present both if you run |
I have removed the use of vmap completely on the issue_80 branch. Instead the modelsim.ini file is manipulated directly from Python. Could you give it a try? |
The issue_80 branch now works for me. I can confirm that the bug is present even when I run vmap as a stand alone binary. |
I have integrated the issue_80 branch into master and made a new release. |
Hi,
There is a bug in the Modelsim 'vmap' command that results in Modelsim incorrectly reporting that the 'modelsim.ini' file has been successfully modified, when in fact 'modelsim.ini' has not been modified. The result is compilation failure.
This bug only occurs on some Linux hosts. Specifically, I'm now experiencing it when running Modelsim Altera on CentOS 7 (also on CentOS 6.5).
It would be nice if there was a workaround for this issue in vUnit. vUnit would have to detect that the vmap bug exists, and then modify 'modelsim.ini' without using the 'vmap' command.
Regards,
Daniel Blomkvist
The text was updated successfully, but these errors were encountered: