caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Nicolas Boulay <nicolas@boulay.name>
To: OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Errors in installing 'lwt'
Date: Tue, 21 Oct 2014 22:55:21 +0200	[thread overview]
Message-ID: <CAH+PdrAkaud0_jWTwyThvZ+kfNawMnJf-hcakdwNXt9VBjcm7w@mail.gmail.com> (raw)
In-Reply-To: <54461AFF.9010407@inria.fr>

[-- Attachment #1: Type: text/plain, Size: 1448 bytes --]

it works, but it seems that there is no dependancies checking on c library
like zlib, ssl, sqllite,...

Those "devel" library should be installed by "hand" or does i miss
something ? Is there a way to find all external dependancies list ?

2014-10-21 10:36 GMT+02:00 Francois Berenger <francois.berenger@inria.fr>:

> try and see
>
> On 10/21/2014 10:18 AM, Nicolas Boulay wrote:
>
>> Does a dependancies on the version of opam it-self exist ? Does a one
>> year old opam binaries could do the job ? (mageia 4)
>>
>> 2014-10-20 19:59 GMT+02:00 Török Edwin <edwin+ml-ocaml@etorok.net
>> <mailto:edwin+ml-ocaml@etorok.net>>:
>>
>>     On 10/20/2014 07:37 PM, Helmut Brandl wrote:
>>     > Thanks a lot Edwin,
>>     >
>>     > after the reinstallation of 'ocamlfind' everythink worked fine. I
>> have now 'lwt' and 'js_of_ocaml' successfully installed on the system
>> switch.
>>
>>     Thanks, I was able to create a testcase and I opened an issue about
>>     improving the camlp4+system package here:
>>     https://github.com/ocaml/opam-repository/issues/2900
>>
>>     Best regards,
>>     --Edwin
>>
>>
>>     --
>>     Caml-list mailing list.  Subscription management and archives:
>>     https://sympa.inria.fr/sympa/arc/caml-list
>>     Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>>     Bug reports: http://caml.inria.fr/bin/caml-bugs
>>
>>
>>
> --
> Regards,
> Francois.
>

[-- Attachment #2: Type: text/html, Size: 2758 bytes --]

  parent reply	other threads:[~2014-10-21 20:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-20 13:59 Helmut Brandl
2014-10-20 14:14 ` Török Edwin
2014-10-20 15:06   ` helmut.brandl
2014-10-20 16:21     ` Török Edwin
2014-10-20 16:37       ` Helmut Brandl
2014-10-20 17:59         ` Török Edwin
2014-10-21  8:18           ` Nicolas Boulay
     [not found]             ` <54461AFF.9010407@inria.fr>
2014-10-21 20:55               ` Nicolas Boulay [this message]
2014-10-21 21:25                 ` Török Edwin
     [not found] ` <544518F1.4050907@inria.fr>
     [not found]   ` <544519B6.6050007@gmx.net>
     [not found]     ` <54451A2A.6010300@inria.fr>
2014-10-20 14:44       ` Helmut Brandl
2014-10-20 14:50         ` John Whitington
2014-10-20 14:56           ` Helmut Brandl
2014-10-20 15:03             ` Helmut Brandl
2014-10-20 15:08             ` Francois Berenger
2014-10-20 15:19               ` Helmut Brandl
2014-10-20 15:25                 ` Francois Berenger
2014-10-20 16:24                   ` Helmut Brandl
2014-10-20 16:50                     ` Marek Kubica
2014-10-20 15:30                 ` Daniel Bünzli

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=CAH+PdrAkaud0_jWTwyThvZ+kfNawMnJf-hcakdwNXt9VBjcm7w@mail.gmail.com \
    --to=nicolas@boulay.name \
    --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).