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

A second run of make uses the mirage tool available into the duniverse repository #330

Open
dinosaure opened this issue Mar 3, 2022 · 0 comments

Comments

@dinosaure
Copy link
Member

It's a bit strange and I did not introspect too much the problem but it seems that a second make uses the mirage tool available into the duniverse directory. At least, a concurrent development of the mirage tool with opam pin and mirage-skeleton put me into some troubles about which version of mirage I used to do mirage configure.

This issue is mostly to keep track on such behavior: if it's expected or not and if someone got a similar problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant