From: rrbq <rrbq@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: zeroinstall: build fails with "Alert deprecated: module Stdlib.Stream Use the camlp-streams library instead."
Date: Mon, 20 Jun 2022 12:18:19 +0200 [thread overview]
Message-ID: <20220620101819.K_fpup0HeIWuGL5zWSsKpR7I49zpRiD16F-mNew2I5w@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37614@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
New comment by rrbq on void-packages repository
https://github.com/void-linux/void-packages/issues/37614#issuecomment-1160206326
Comment:
Hello. I would like to point out something else. As Dune is invoked with `--profile=release`, this deprecation warning (OCaml calls it an "alert") [should be non-fatal](https://dune.readthedocs.io/en/stable/faq.html#how-to-make-warnings-non-fatal).
The real problem should be this:
```
File "src/support/json.ml", line 3, characters 9-26:
3 | type t = Yojson.Basic.json
^^^^^^^^^^^^^^^^^
Error: Unbound type constructor Yojson.Basic.json
```
There's a commit in the 0install repo that addresses this issue: https://github.com/0install/0install/commit/70b6047.
zeroinstall should build successfully if the changes from that commit are applied, the deprecation alerts can be ignored...until OCaml 5.0 is released (and Void upgrades to it), then camlp-streams will have to be used (or [maybe not](https://github.com/0install/0install/commit/b3d7e5f) :-)).
prev parent reply other threads:[~2022-06-20 10:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 20:26 [ISSUE] " paper42
2022-06-20 9:31 ` rrbq
2022-06-20 9:38 ` rrbq
2022-06-20 9:45 ` rrbq
2022-06-20 9:47 ` rrbq
2022-06-20 10:18 ` rrbq [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220620101819.K_fpup0HeIWuGL5zWSsKpR7I49zpRiD16F-mNew2I5w@z \
--to=rrbq@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).