feat(pkg): use the relocatable compiler#14357
Conversation
a2b87f1 to
dba99db
Compare
Signed-off-by: Ali Caglayan <alizter@gmail.com>
The relocatable-compiler package installs libraries (including threads, str, unix) under target/lib/ocaml/, matching the layout of other compiler packages. Without being listed in compiler_package_names, install_roots did not append the /ocaml subdirectory to its lib_root, causing dev-tools like utop to fail with "Library threads not found". Signed-off-by: Ali Caglayan <alizter@gmail.com>
dba99db to
10f294f
Compare
|
Can you fill me in with the current state? The way I was explained this many months ago is that OCaml 5.5 is relocatable by default and the relocatable patches will be backported to older compilers in point releases. in such case it would just work out of the box for everyone without need for more overlays. Is that not the case anymore? |
|
@Leonidas-from-XIV That is the case for OCaml 5.5 which is yet to be released. You can constrain your dependencies to use it. The support provided by David's repository is for older versions to at least 4.14. It takes time for patches to make their way to the compiler branch, and I'm not even certain that it has been agreed yet that this will be the case. For users of dune pkg, we can and should make use of it however. |
|
Yes, but my question was about the backports to older compiler releases. Are these not planned anymore? |
|
I don't know. I don't know if it has been discussed with the compiler developers yet and I also don't know if these discussions have happened with opam. My point is that we don't need to know any of this to make use of it in dune. |
|
@dra27 could you provide us with some insight on what the plan is for the backporting (or lack thereof) for older compilers? |
This PR enables the relocatable compiler by making it the default. It does so by using David's relocatable opam-repository as a second set of overlays.
The order is now
overlay,relocatable,upstream.This is part of the work on:
The following need to be done:
In order to test, clone your favourite OCaml project. Run
dune build --pkg enabledand wait. Then when it's finished delete_build/and run again. If all goes well (and your cache is actually enabled) it should restore from cache.Any issues please report here together with your first and second trace files.
_build/trace.csexpand_build/trace.csexp.old.