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.

Sign up for GitHub

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

Jump to bottom

It's difficult to make use of -runtime-variants #7926

Closed
vicuna opened this issue Feb 20, 2019 · 4 comments
Closed

It's difficult to make use of -runtime-variants #7926

vicuna opened this issue Feb 20, 2019 · 4 comments
Labels
feature-wish platform-support

Comments

@vicuna
Copy link

vicuna commented Feb 20, 2019

Original bug ID: 7926
Reporter: lortex
Status: new
Resolution: open
Priority: normal
Severity: feature
Category: platform support (windows, cross-compilation, etc)
Monitored by: @nojb @gasche

Bug description

Currently, it's not possible to choose a custom variant unless libasmrun.a is installed in the ocaml library directory.
In most situations it's not a problem as any opam package could go and install its runtime variant in '/lib/ocaml'.
However it's not possible to do that if ocaml is a system compiler (installed in '/usr/lib/ocaml' for example) because of permissions issues.

Is there a workaround ?
Is it possible to add an option to specify the runtime variant location ?
@dbuenzli
Copy link
Contributor

See @TheLortex's PR #2309 (whose name should be changed to reflect what it does).

@gasche
Copy link
Member

gasche commented Mar 16, 2019

I'll note that @TheLortex discovered (in the process of implementing the PR above) that -I <path> actually works to indicate alternate directories for runtime variant, solving the immediate issue describing in this ticket (so I'm closing this). But we are discussed better / more discoverable ways to do these things.

@gasche gasche closed this as completed Mar 16, 2019
@hannesm hannesm mentioned this issue Mar 16, 2019
Merged
@dbuenzli
Copy link
Contributor

Note that -I path is in general unfriendly for incremental build systems. That said I'm not sure why you closed the issue while the corresponding PR to solve this problem has not been merged.

@gasche
Copy link
Member

gasche commented Mar 16, 2019

If I understand correctly, the issue as described is "I can't build my own runtime variants unless I install the .a in ocamlc -where"; this issue is entirely solved by using the -I flag -- although I believe we still have an ergonomics/usability problem with this workaround. The PR solves a more general problem that you helped identify, so I think the two are not directly related anymore.

Also, apparently it's PR-closing time after the migration, I didn't want to be left behind!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature-wish platform-support
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@gasche @dbuenzli @vicuna