From: Richard Jones <rich@annexia.org>
To: caml-list@inria.fr
Subject: Strange, occasional build failure with ocamlmklib / ranlib
Date: Tue, 2 Jun 2009 15:46:27 +0100 [thread overview]
Message-ID: <20090602144627.GA20574@annexia.org> (raw)
I just want to post this here in case it rings a bell with anyone:
ocamlfind ocamlc -c guestfs.mli
ocamlfind ocamlc -c guestfs.ml
ocamlfind ocamlopt -c guestfs.ml
ocamlmklib -o mlguestfs guestfs_c.o guestfs_c_actions.o guestfs.cmo
-L../src/.libs -lguestfs
ocamlmklib -o mlguestfs guestfs_c.o guestfs_c_actions.o guestfs.cmx
-L../src/.libs -lguestfs
ranlib: './libmlguestfs.a': No such file
There's no other error visible.
The error is intermittent, and fairly rare. Usually if we just run
the build again it succeeds.
We've seen the same bug happening on 3.09.3 and on 3.11.1+rc0.
There are more detailed build logs here:
https://bugzilla.redhat.com/show_bug.cgi?id=502309
Anyone got any ideas at all?
Rich.
--
Richard Jones
Red Hat
next reply other threads:[~2009-06-02 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 14:46 Richard Jones [this message]
2009-06-02 14:52 ` [Caml-list] " Richard Jones
2009-06-02 14:53 ` Olivier Andrieu
2009-06-02 14:53 ` Martin Jambon
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=20090602144627.GA20574@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;
as well as URLs for NNTP newsgroup(s).