From: oliver <oliver@first.in-berlin.de>
To: Roberto Di Cosmo <roberto@dicosmo.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Old and new OCaml installed on same machine?
Date: Mon, 25 Feb 2013 01:50:39 +0100 [thread overview]
Message-ID: <20130225005039.GA8816@siouxsie> (raw)
In-Reply-To: <CAJBwKuUzOa+SwJ=EKw_+X5zRhe6zzt_krzmGcpqjmohtZHXihg@mail.gmail.com>
Hello Roberto,
On Mon, Feb 18, 2013 at 08:34:35AM +0100, Roberto Di Cosmo wrote:
> Dear Oliver,
> just use the Opam package manager for OCaml and you will be fine.
[...]
Do you mean something like ths following?!
===================================================================
oliver@siouxsie:~$ . ocamlbrew/ocaml-4.00.1/etc/ocamlbrew.bashrc
oliver@siouxsie:~$ opam install ocurl
The following actions will be performed:
- install ocurl.0.5.4
1 to install | 0 to reinstall | 0 to upgrade | 0 to downgrade | 0 to remove
=-=-= ocurl.0.5.4 =-=-=
The archive for ocurl.0.5.4 is in the local cache.
Extracting /home/oliver/ocamlbrew/ocaml-4.00.1/.opam/archives/ocurl.0.5.4+opam.tar.gz.
Building ocurl.0.5.4:
./configure
make
make install
The compilation of ocurl.0.5.4 failed.
Uninstalling ocurl.0.5.4:
ocamlfind remove curl
==== ERROR [while installing ocurl.0.5.4] ====
# command make
# path /home/oliver/ocamlbrew/ocaml-4.00.1/.opam/4.00.1/build/ocurl.0.5.4
# exit-code 2
# env-file /home/oliver/ocamlbrew/ocaml-4.00.1/.opam/4.00.1/build/ocurl.0.5.4/ocurl-1872ec.env
# stdout-file /home/oliver/ocamlbrew/ocaml-4.00.1/.opam/4.00.1/build/ocurl.0.5.4/ocurl-1872ec.out
# stderr-file /home/oliver/ocamlbrew/ocaml-4.00.1/.opam/4.00.1/build/ocurl.0.5.4/ocurl-1872ec.err
### stdout ###
make[1]: Entering directory `/home/oliver/ocamlbrew/ocaml-4.00.1/.opam/4.00.1/build/ocurl.0.5.4'
make[1]: Leaving directory `/home/oliver/ocamlbrew/ocaml-4.00.1/.opam/4.00.1/build/ocurl.0.5.4'
make[1]: Entering directory `/home/oliver/ocamlbrew/ocaml-4.00.1/.opam/4.00.1/build/ocurl.0.5.4'
ocamlc.opt -c curl.mli -o curl.cmi
ocamlc.opt -c curl.ml -o curl.cmo
ocamlc.opt -c -ccopt "-DHAVE_CONFIG_H -Wall" curl-helper.c
make[1]: Leaving directory `/home/oliver/ocamlbrew/ocaml-4.00.1/.opam/4.00.1/build/ocurl.0.5.4'
### stderr ###
...[truncated]
curl-helper.c:5460: error: for each function it appears in.)
curl-helper.c:5460: warning: type defaults to ‘int’ in declaration of ‘_curl_opt’
curl-helper.c: In function ‘handleDnsServers’:
curl-helper.c:5488: error: ‘CURLOPT_DNS_SERVERS’ undeclared (first use in this function)
curl-helper.c:5488: warning: type defaults to ‘int’ in declaration of ‘_curl_opt’
curl-helper.c: At top level:
curl-helper.c:6119: error: ‘CURL_VERSION_TLSAUTH_SRP’ undeclared here (not in a function)
curl-helper.c:6120: error: ‘CURL_VERSION_NTLM_WB’ undeclared here (not in a function)
make[1]: *** [curl-helper.o] Error 2
make: *** [all] Error 2
'opam install ocurl' failed.
oliver@siouxsie:~$
===================================================================
Ciao,
Oliver
next prev parent reply other threads:[~2013-02-25 0:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 7:22 oliver
2013-02-18 7:34 ` Roberto Di Cosmo
2013-02-18 14:16 ` oliver
2013-02-25 0:50 ` oliver [this message]
2013-02-25 1:26 ` Francois Berenger
2013-02-25 2:09 ` oliver
2013-02-25 8:07 ` Gabriel Kerneis
2013-02-25 9:03 ` Gabriel Scherer
2013-02-27 1:28 ` oliver
2013-02-18 7:43 ` Francois Berenger
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=20130225005039.GA8816@siouxsie \
--to=oliver@first.in-berlin.de \
--cc=caml-list@inria.fr \
--cc=roberto@dicosmo.org \
/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).