Summary: | devel/ocaml-camlp4 missing some files | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | mmatalka |
Component: | Individual Port(s) | Assignee: | freebsd-ports-bugs (Nobody) <ports-bugs> |
Status: | Closed FIXED | ||
Severity: | Affects Some People | CC: | johans, michipili, mmatalka |
Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(michipili) |
Version: | Latest | ||
Hardware: | amd64 | ||
OS: | Any |
Description
mmatalka
2015-05-06 05:37:55 UTC
I installed ocaml and camlp4 via 'pkg' btw, not from port source. On my system, I have a camlp4 META file installed by ocaml-findlib-1.5.5, but on some other system using ocaml-findlib-1.5.5_1 this file is absent. @mmatalka – What is your version of ocaml-findlib? @johan I CCed you because it seems to me, the issue is related to findlib. pkg which /usr/local/lib/ocaml/site-lib/camlp4/META /usr/local/lib/ocaml/site-lib/camlp4/META was installed by package ocaml-findlib-1.5.5 (In reply to Michael Grünewald from comment #2) I have 1.5.5_1, I only installed it to see if it fixed the problem because opam always installs its own findlib. Without findlib installed, though, I have no site-lib dir. With it installed I do, but no camlp4 directory in it. findlib will install the META file for camlp4 if it is present already when findlib is installed. Since camlp4 used to be a part of ocaml, this was always the case in previous versions. But now it depends on the order in which findlib and camlp4 are installed. Since other ports depend on findlib's META files for camlp4, I will add camlp4 as an explicit dependency of findlib. Hopefully this will resolve the issue. A commit references this bug: Author: johans Date: Wed May 6 07:20:47 UTC 2015 New revision: 385508 URL: https://svnweb.freebsd.org/changeset/ports/385508 Log: Add dependency on camlp4 to ensure its META data gets installed PR: 199986 Changes: head/devel/ocaml-findlib/Makefile head/devel/ocaml-findlib/pkg-plist Great that you fixed this os quickly Johan. Thanks! I have closed this PR as I believe the issue is resolved now. Do reopen it again if the fix is not complete. (In reply to Johan van Selst from comment #7) Thank you for the quick response! |