-
Notifications
You must be signed in to change notification settings - Fork 412
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
Regression from 1.6 to 1.7 for libraries with archives in subdirectories #1885
Comments
That's definitely a bug in Dune. The |
ghost
mentioned this issue
Feb 27, 2019
ghost
pushed a commit
that referenced
this issue
Feb 27, 2019
Fix #1885 Signed-off-by: Jeremie Dimino <jeremie@dimino.org>
rgrinberg
pushed a commit
that referenced
this issue
Feb 27, 2019
Fix #1885 Signed-off-by: Jeremie Dimino <jeremie@dimino.org>
rgrinberg
added a commit
to rgrinberg/opam-repository
that referenced
this issue
Feb 27, 2019
CHANGES: - Fix interpretation of `META` files containing archives with `/` in the filename. For instance, this was causing llvm to be unusable with dune (ocaml/dune#1889, fix ocaml/dune#1885, @diml) - Make errors about menhir stanzas be located (ocaml/dune#1881, fix ocaml/dune#1876, @diml)
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm seeing build failures with 1.7.* that work well with 1.6.3, in particular due to bec9fbb from #1329.
I don't have a self-contained repro yet, but figured I'd open an issue in case there are any quick comments. The symptom is warnings (that a later commit makes into errors) such as:
This come from building a library with
(libraries llvm.analysis ...)
in itsdune
. Note that thellvm_analysis.cmxa
file is actually present as/Users/jjb/.opam/sledge/lib/llvm/static/llvm_analysis.cmxa
. Note the addedstatic
directory. This comes from theMETA.llvm
file, which declares packages with archives in thestatic
subdirectory:I don't know if
META
files are not supposed to do that, but it worked with dune 1.6.FWIW, looking at the patch, the use of
basename
here looked suspicious to me.The text was updated successfully, but these errors were encountered: