From: "Richard W.M. Jones" <rich@annexia.org>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Test failure - why?
Date: Fri, 26 Apr 2019 12:41:42 +0100 [thread overview]
Message-ID: <20190426114142.k7qibozcshqxdk5r@annexia.org> (raw)
In-Reply-To: <20190426100744.GA5136@prajna.paris.inria.fr>
On Fri, Apr 26, 2019 at 12:07:44PM +0200, Sébastien Hinderer wrote:
> Did you try to run the command manually to see what happens?
There's a bit more to this - when I run it from a straight git
checkout it (of course) doesn't fail. It only fails when I build the
Fedora package.
However I did preserve the Fedora build root just now and was able to
run the command by hand there, and the error is:
Fatal error: unknown C primitive `unix_fsync'
I suppose it must be linking to the wrong OCaml runtime - perhaps the
installed one (4.07.0)?
Rich.
next prev parent reply other threads:[~2019-04-26 11:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 9:48 Richard W.M. Jones
2019-04-26 10:07 ` Sébastien Hinderer
2019-04-26 11:32 ` Gabriel Scherer
2019-04-26 11:41 ` Richard W.M. Jones [this message]
2019-04-26 12:03 ` Nicolás Ojeda Bär
2019-05-13 12:54 ` Sébastien Hinderer
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=20190426114142.k7qibozcshqxdk5r@annexia.org \
--to=rich@annexia.org \
--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