From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: Matej Kosik <5764c029b688c1c0d24a2e97cd764f@gmail.com>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] [ANN] Batteries 2.5.0, compatible with OCaml 4.03
Date: Fri, 13 May 2016 07:56:48 -0400 [thread overview]
Message-ID: <CAPFanBE2VnzyHZsR0ShZY9Q6oxJRY4k5GNQSu8ALEiC+o2RVnw@mail.gmail.com> (raw)
In-Reply-To: <5735975B.4000200@gmail.com>
There is indeed a packaging problem with 2.5.0 -- I did two quick
bugfix releases in succession, and 2.5.2 should land in opam any time
now. Apologies for the hiccup.
On Fri, May 13, 2016 at 4:59 AM, Matej Kosik
<5764c029b688c1c0d24a2e97cd764f@gmail.com> wrote:
> Hi,
>
> On 05/13/2016 09:53 AM, Christoph Höger wrote:
>> Unfortunately, I am unable to use some modules:
>>
>> consider the following simple test:
>>
>> % cat foo.ml
>> let () = Printf.printf "%s\n" Batteries.Sys.os_type
>> % ocamlbuild -pkg batteries foo.native
>> ...
>> File "_none_", line 1:
>> Error: No implementations provided for the following modules:
>> BatConcreteQueue_402 referenced from
>> [..]/opam/4.02.3/lib/batteries/batteries.cmxa(BatQueue)
>> BatOpaqueInnerSys referenced from
>> [..]/opam/4.02.3/lib/batteries/batteries.cmxa(BatSys)
>> Command exited with code 2.
>>
>> This is opam 1.2.2, OCaml 4.02.3 and batteries 2.5.0
>>
>> Did I break something or is this an actual bug?
>
> In my context, after switching to 4.02.3, I noticed the same problem.
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
prev parent reply other threads:[~2016-05-13 11:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 14:41 Gabriel Scherer
2016-05-13 7:53 ` Christoph Höger
2016-05-13 8:59 ` Matej Kosik
2016-05-13 11:56 ` Gabriel Scherer [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=CAPFanBE2VnzyHZsR0ShZY9Q6oxJRY4k5GNQSu8ALEiC+o2RVnw@mail.gmail.com \
--to=gabriel.scherer@gmail.com \
--cc=5764c029b688c1c0d24a2e97cd764f@gmail.com \
--cc=caml-list@inria.fr \
/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).