From: Florent Monnier <monnier.florent@gmail.com>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: Edgar Friendly <thelema314@gmail.com>, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] [ANN] Batteries 2.1
Date: Sun, 21 Jul 2013 21:43:14 +0200 [thread overview]
Message-ID: <CAE1DttDUivUuxj8E_mffUhc0xw2OgCV5q2y5wzAfedfTutwNAw@mail.gmail.com> (raw)
In-Reply-To: <CAPFanBGbOSbRMOJCePmaUutN0Mfy4T6R0C9tJhqDahAF2irtFA@mail.gmail.com>
2013/07/21, Gabriel Scherer wrote:
> I don't think Batteries needs bisect to compile -- I regularly build
> Batteries on systems without bisect. That should be an optional
> dependency (using for testing and development purposes), but it's
> fairly possible that the buildsystem displays a not-nice warning when
> it's missing that you considered an error.
It's not only a "not-nice warning",
nothing is build at all.
$ make
Build mode: shared
ocamlbuild -no-links src/batteries.cma src/batteriesHelp.cmo
src/batteriesThread.cma META src/batteries.cmxs
src/batteriesThread.cmxs
ocamlfind: Package `bisect' not found
''ocamlfind ocamldep -package bigarray,num,str -modules
src/batInnerPervasives.ml > src/batInnerPervasives.ml.depends
Exit code 127 while executing this command:
''ocamlfind ocamldep -package bigarray,num,str -modules
src/batInnerPervasives.ml > src/batInnerPervasives.ml.depends
Makefile:71: recipe for target `all' failed
make: *** [all] Error 127
$ tree -fi | grep 'cmi$'
# there is nothing
$ tree -fi | grep 'cmo$'
# there is nothing
$ tree -fi | grep 'cmx$'
./_build/myocamlbuild.cmx
$ tree -fi | grep 'cma$'
# there is nothing
$ tree -fi | grep 'cmxa$'
# there is nothing
If the upstreams don't have a MS/Windows test environment, I'm
volunteer for "minimal reports": I mean whenever they want they can
send me a snapshot (or a link to it, or scm or whatever), I run `make`
and send them back the error message.
I can compile it myself I really don't mind, but doing this way is not
very wellcoming for beginners.
--
Regards
next prev parent reply other threads:[~2013-07-21 19:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 13:50 Edgar Friendly
2013-07-19 9:59 ` Sébastien Dailly
2013-07-22 7:41 ` Francois Berenger
2013-07-22 7:54 ` Sébastien Dailly
2013-07-21 13:32 ` Florent Monnier
2013-07-21 16:29 ` Gabriel Scherer
2013-07-21 19:43 ` Florent Monnier [this message]
2013-07-21 20:02 ` rixed
2013-07-22 8:02 ` Florent Monnier
2013-07-22 13:11 ` Nicolas Braud-Santoni
2013-07-23 3:47 ` Florent Monnier
2013-07-22 20:38 ` rixed
2013-07-23 6:13 ` rixed
2013-07-23 6:55 ` Gabriel Scherer
2013-07-23 10:40 ` Florent Monnier
2013-07-21 20:13 ` Marek Kubica
2013-07-21 20:02 ` Marek Kubica
2013-07-22 14:49 ` Edgar Friendly
2013-07-23 10:56 ` [Caml-list] " Sylvain Le Gall
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=CAE1DttDUivUuxj8E_mffUhc0xw2OgCV5q2y5wzAfedfTutwNAw@mail.gmail.com \
--to=monnier.florent@gmail.com \
--cc=caml-list@inria.fr \
--cc=gabriel.scherer@gmail.com \
--cc=thelema314@gmail.com \
/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