caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Kenneth Adam Miller <kennethadammiller@gmail.com>
To: Iguernlala Mohamed <mohamed.iguernelala@gmail.com>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Massive Memory Consumption
Date: Mon, 29 Jun 2015 11:13:39 -0400	[thread overview]
Message-ID: <CAK7rcp_T-rVxZnpF21AaUif3=3JN4kJ4P2+bSJARBCkudoaM6A@mail.gmail.com> (raw)
In-Reply-To: <558F63B9.3050502@gmail.com>

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

Having trouble installing ocp-memprof:

opam switch 4.01.0+ocp1-20150202
opam install core # that gives the below error

#=== ERROR while installing lwt.2.4.5
=========================================#
# opam-version 1.2.0
# os           linux
# command      ./configure --disable-libev --enable-react --disable-ssl
--enable-unix --enable-extra --disable-preemptive --disable-glib
--disable-text
# path
/home/kennethadammiller/.opam/4.01.0+ocp1-20150202/build/lwt.2.4.5
# compiler     4.01.0+ocp1-20150202
# exit-code    1
# env-file
/home/kennethadammiller/.opam/4.01.0+ocp1-20150202/build/lwt.2.4.5/lwt-9302-90b366.env
# stdout-file
 /home/kennethadammiller/.opam/4.01.0+ocp1-20150202/build/lwt.2.4.5/lwt-9302-90b366.out
# stderr-file
 /home/kennethadammiller/.opam/4.01.0+ocp1-20150202/build/lwt.2.4.5/lwt-9302-90b366.err
### stderr ###
# E: Cannot find buildable internal library 'lwt-preemptive' when checking
build depends
# E: Failure("1 configuration error")


#=== ERROR while installing typerep.111.17.00
=================================#
# opam-version 1.2.0
# os           linux
# command      make
# path
/home/kennethadammiller/.opam/4.01.0+ocp1-20150202/build/typerep.111.17.00
# compiler     4.01.0+ocp1-20150202
# exit-code    2
# env-file
/home/kennethadammiller/.opam/4.01.0+ocp1-20150202/build/typerep.111.17.00/typerep-8640-062a54.env
# stdout-file
 /home/kennethadammiller/.opam/4.01.0+ocp1-20150202/build/typerep.111.17.00/typerep-8640-062a54.out
# stderr-file
 /home/kennethadammiller/.opam/4.01.0+ocp1-20150202/build/typerep.111.17.00/typerep-8640-062a54.err
### stdout ###
# ...[truncated]
# Re-raised at file "driver/compile.ml", line 120, characters 10-11
# Called from file "driver/optmain.ml", line 234, characters 25-26
# Called from file "arg.ml", line 252, characters 11-20
# Called from file "arg.ml", line 264, characters 4-32
# Called from file "driver/optmain.ml", line 234, characters 25-26
# Re-raised at file "driver/errors.ml", line 79, characters 33-34
# Called from file "format.ml", line 1197, characters 8-23
# Called from file "driver/optmain.ml", line 234, characters 25-26
# Called from file "driver/optmain.ml", line 234, characters 25-26
# Command exited with code 2.
### stderr ###
# W: Cannot find source file matching module 'typerep_generics_sexprep' in
library typerep_generics_sexprep
# W: Cannot find source file matching module 'typerep_extended' in library
typerep_extended
# W: Cannot find source file matching module 'typerep_lib' in library
typerep_lib
# E: Failure("Command
''/home/kennethadammiller/.opam/4.01.0+ocp1-20150202/bin/ocamlbuild'
lib/typerep_lib.cma lib/typerep_lib.cmxa lib/typerep_lib.a
lib/typerep_lib.cmxs syntax/with_typerep/typerep_syntax.cma
syntax/with_typerep/typerep_syntax.cmxa
syntax/with_typerep/typerep_syntax.a
syntax/with_typerep/typerep_syntax.cmxs extended/lib/typerep_extended.cma
extended/lib/typerep_extended.cmxa extend...[truncated]
# make: *** [build] Error 1

I'll switch to the other version of ocp and try and build install core,
possibly it's a compiler and package version combination thing...


On Sat, Jun 27, 2015 at 11:02 PM, Iguernlala Mohamed <
mohamed.iguernelala@gmail.com> wrote:

>  If you plan to release it, I guess that it will be open source (?). So,
> you should be able to use
> the online (public) version of ocp-memprof if you don't want/cannot
> request for a private
> version.
>
>
>
> Le 27/06/2015 20:26, Kenneth Adam Miller a écrit :
>
> Well I can release it, but I was planning on integrating it into a
> library. Can we share with one another somehow so that it's just
> temporarily private?
>
> On Sat, Jun 27, 2015 at 1:52 PM, Iguernlala Mohamed <
> mohamed.iguernelala@gmail.com> wrote:
>
>> Hi,
>>
>> Can you elaborate ? What is the kind of tool you would like to profile ?
>> - open-source vs closed-source ?
>> - commercial or not ?
>> - ...
>>
>> Regards,
>> Mohamed Iguernlala.
>>
>>
>>
>> Le 27/06/2015 15:38, Kenneth Adam Miller a écrit :
>>
>>> So, I saw that ocp-memprof is private, so I was looking for an
>>> alternative. What kind of other profiling tools for ocaml are out there?
>>>
>>
>>
>
>

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

  reply	other threads:[~2015-06-29 15:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-27 14:38 Kenneth Adam Miller
2015-06-27 17:52 ` Iguernlala Mohamed
2015-06-27 19:26   ` Kenneth Adam Miller
2015-06-28  3:02     ` Iguernlala Mohamed
2015-06-29 15:13       ` Kenneth Adam Miller [this message]
2015-06-29 16:29         ` Iguernlala Mohamed

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='CAK7rcp_T-rVxZnpF21AaUif3=3JN4kJ4P2+bSJARBCkudoaM6A@mail.gmail.com' \
    --to=kennethadammiller@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=mohamed.iguernelala@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).