-
Notifications
You must be signed in to change notification settings - Fork 29
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
build error: bad module difinition #61
Comments
Thanks @kahsa this is a known issue and will be fixed soon, I will update you here. |
@kahsa is this still relevant? I think this has been fixed in V since? |
It still does this in my environment, but not in yours?
Whatever it is, it's not caused by vab, so it should be brought to V issue. |
Hmm ok I see - it's because it's in |
Yes, this bug is still around, and has been for too long. The workaround is to move the module somewhere else (anywhere other than |
Cannot link directories on MacOS. Though beyond the scope of this repo, I think this issue (as well as general workflow perk of not needing to adopt a specific development directory) could be tackled by using a specialized mod file (or some other type of config) in the Imo, from the user side it should feel like running |
OS: ArchLinux
V version: 0.2.2 a73c209
vab doctor
What did you do?
~/.vmodules/vab% v vab.v
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered: