From: "Stéphane Glondu" <steph@glondu.net>
To: Joel Reymont <joelr1@gmail.com>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] cvs ocaml build failing
Date: Thu, 16 Apr 2009 18:50:59 +0200 [thread overview]
Message-ID: <49E761F3.9030004@glondu.net> (raw)
In-Reply-To: <be68c3dc0904160930g106490b6r44b2dbff8e551daf@mail.gmail.com>
Joel Reymont a écrit :
>> That would be my fault (I guess). See PR#3047. I haven't tested the
>> patch with the ocamlbuild-based build system, but I guess "initgroups.o"
>> and "setgroups.o" are missing from otherlibs/unix/libunix.clib... Could
>> you check that updating libunix.clib solves your build failure?
>
> How do I check?
Add initgroups.o and setgroups.o in otherlibs/unix/libunix.clib, then
launch again the compilation.
> BTW, there was another error with regular make process.
>
> boot/ocamlrun boot/ocamlc -nostdlib -I boot -linkall -o ocaml.tmp
> toplevel/toplevellib.cma toplevel/topstart.cmo
> File "_none_", line 1, characters 0-1:
> Error: Error while linking boot/stdlib.cma(Pervasives):
> The external function `caml_log1p_float' is not available
> make[1]: *** [ocaml] Error 2
It seems that -lm is missing in BYTECCLIBS and/or NATIVECCLIBS (see
config/Makefile). However, the ./configure script should have done this
for you. This might be worth a bugreport.
Please pay attention and don't mix both build systems: either use make
or ocamlbuild, but don't run make after having used ocamlbuild nor
vice-versa. To be sure, start from a fresh CVS checkout.
Cheers,
--
Stéphane
next prev parent reply other threads:[~2009-04-16 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 13:04 Joel Reymont
2009-04-16 16:16 ` [Caml-list] " Stéphane Glondu
[not found] ` <be68c3dc0904160930g106490b6r44b2dbff8e551daf@mail.gmail.com>
2009-04-16 16:50 ` Stéphane Glondu [this message]
2009-04-16 17:14 ` Joel Reymont
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=49E761F3.9030004@glondu.net \
--to=steph@glondu.net \
--cc=caml-list@inria.fr \
--cc=joelr1@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;
as well as URLs for NNTP newsgroup(s).