caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Helmut Brandl <helmut.brandl@gmx.net>
Cc: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Problems installing with opam
Date: Mon, 28 Mar 2016 07:14:00 -0600	[thread overview]
Message-ID: <56F92E18.9000401@gmx.net> (raw)
In-Reply-To: <CAGmVoG0oP+BQyvndy0h85K0uYbT9dhXUW0Sm63Up-RkVG9Z_Pg@mail.gmail.com>

Isn't there another way than patching. I just want to install 
"js_of_ocaml" and use it. However "js_of_ocam" requires "lwt" which 
requires "camlp4". All these packages are oficial packages in the opam 
repository. I.e. they should be installable with opam without patching.

If I understand you correctly you are saying that the opam repository is 
inconsistent and nobody can install "camlp4", "lwt" and "js_of_ocaml" 
using some 4.x.x compiler of "ocaml". Why not fix the problem?

Or did I get something wrong?

Regards
Helmut

On 03/28/2016 06:51 AM, Kakadu wrote:
> I'm saying that you can't install
> 1) camlp4 4.02.0-1modular-implicits using normal compiler
> 2) camlp4 4.02.0-1 using ocaml-with-modular-implicits-compiler
>
> 2016-03-28 16:44 GMT+04:00 Helmut Brandl <helmut.brandl@gmx.net>:
>> Are you saying that I cannot install "camlp4" with opam?
>>
>>
>> On 03/28/2016 06:37 AM, Kakadu wrote:
>>> There are some changes in compiler which supports modular implicits. I
>>> have patched some packages. Camlp4 too, AFAIR
>>>
>>> https://github.com/Ostapers/Ostapers.github.io/tree/master/opam/packages
>>>
>>> Happy hacking,
>>>
>>> 2016-03-28 16:32 GMT+04:00 Helmut Brandl <helmut.brandl@gmx.net>:
>>>> The program "pkg-config" was not on my system. Installing it, I could at
>>>> least continue. However now I get problems installing "camlp4". The
>>>> compilation of "camlp4" seems to fail.
>>>>
>>>> opam install camlp4
>>>> The following actions will be performed:
>>>>     ∗  install camlp4 4.02.0-1modular-implicits
>>>>
>>>> =-=- Gathering sources
>>>> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>>>> [camlp4] Archive in cache
>>>>
>>>> =-=- Processing actions
>>>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>>>> [ERROR] The compilation of camlp4 failed at "make all".
>>>> Processing  1/1: [camlp4: rm]
>>>> #=== ERROR while installing camlp4.4.02.0-1modular-implicits
>>>> ==================#
>>>> # opam-version 1.2.2
>>>> # os           linux
>>>> # command      make all
>>>> # path
>>>> /home/helmut/.opam/4.02.3/build/camlp4.4.02.0-1modular-implicits
>>>> # compiler     4.02.3
>>>> # exit-code    2
>>>> # env-file
>>>>
>>>> /home/helmut/.opam/4.02.3/build/camlp4.4.02.0-1modular-implicits/camlp4-31525-d2c37b.env
>>>> # stdout-file
>>>>
>>>> /home/helmut/.opam/4.02.3/build/camlp4.4.02.0-1modular-implicits/camlp4-31525-d2c37b.out
>>>> # stderr-file
>>>>
>>>> /home/helmut/.opam/4.02.3/build/camlp4.4.02.0-1modular-implicits/camlp4-31525-d2c37b.err
>>>> ### stdout ###
>>>> # [...]
>>>> # cp /home/helmut/.opam/4.02.3/lib/ocaml/compiler-libs/outcometree.cmi
>>>> camlp4/import/outcometree.cmi
>>>> # cp /home/helmut/.opam/4.02.3/lib/ocaml/compiler-libs/oprint.cmi
>>>> camlp4/import/oprint.cmi
>>>> # cp /home/helmut/.opam/4.02.3/lib/ocaml/compiler-libs/toploop.cmi
>>>> camlp4/import/toploop.cmi
>>>> # /home/helmut/.opam/4.02.3/bin/ocamlc.opt -c -g -w Z -I camlp4/import
>>>> -warn-error A-3 -I camlp4/config -I camlp4 -o
>>>> camlp4/config/Camlp4_config.cmi camlp4/config/Camlp4_config.mli
>>>> # /home/helmut/.opam/4.02.3/bin/ocamlc.opt -c -g -w a -I camlp4/import
>>>> -warn-error A-3 -I camlp4/config -I camlp4/boot -o camlp4/boot/Camlp4.cmo
>>>> camlp4/boot/Camlp4.ml
>>>> # + /home/helmut/.opam/4.02.3/bin/ocamlc.opt -c -g -w a -I camlp4/import
>>>> -warn-error A-3 -I camlp4/config -I camlp4/boot -o camlp4/boot/Camlp4.cmo
>>>> camlp4/boot/Camlp4.ml
>>>> # File "camlp4/boot/Camlp4.ml", line 14607, characters 36-58:
>>>> # Error: Unbound type constructor Asttypes.implicit_flag
>>>> # Command exited with code 2.
>>>> # Makefile:11: recipe for target 'byte' failed
>>>> ### stderr ###
>>>> # + echo camlp4/Camlp4.cmo camlp4/Camlp4Top.cmo camlp4/camlp4prof.byte
>>>> camlp4/mkcamlp4.byte camlp4/camlp4.byte camlp4/camlp4fulllib.cma
>>>> camlp4/camlp4boot.byte camlp4/camlp4boot.cma camlp4/camlp4r.byte
>>>> camlp4/camlp4r.cma camlp4/camlp4rf.byte camlp4/camlp4rf.cma
>>>> camlp4/camlp4o.byte camlp4/camlp4o.cma camlp4/camlp4of.byte
>>>> camlp4/camlp4of.cma camlp4/camlp4oof.byte camlp4/camlp4oof.cma
>>>> camlp4/camlp4orf.byte camlp4/camlp4orf.cma
>>>> camlp4/Camlp4Parsers/Camlp4AstLoader.cmo
>>>> camlp4/Camlp4Parsers/Camlp4DebugParser.cmo
>>>> camlp4/Camlp4Parsers/Camlp4GrammarParser.cmo
>>>> camlp4/Camlp4Parsers/Camlp4ListComprehension.cmo
>>>> camlp4/Camlp4Parsers/Camlp4MacroParser.cmo
>>>> camlp4/Camlp4Parsers/Camlp4OCamlOriginalQuotationExpander.cmo
>>>> camlp4/Camlp4Parsers/Camlp4OCamlParser.cmo
>>>> camlp4/Camlp4Parsers/Camlp4OCamlParserParser.cmo
>>>> camlp4/Camlp4Parsers/Camlp4OCamlReloadedParser.cmo
>>>> camlp4/Camlp4Parsers/Camlp4OCamlRevisedParser.cmo
>>>> camlp4/Camlp4Parsers/Camlp4OCamlRevisedParserParser.cmo
>>>> camlp4/Camlp4Parsers/Camlp4OCamlRevisedQuotationExpander.cmo
>>>> camlp4/Camlp4Parsers/Camlp4QuotationCommon.cmo
>>>> camlp4/Camlp4Parsers/Camlp4QuotationExpander.cmo
>>>> camlp4/Camlp4Printers/Camlp4AstDumper.cmo
>>>> camlp4/Camlp4Printers/Camlp4AutoPrinter.cmo
>>>> camlp4/Camlp4Printers/Camlp4NullDumper.cmo
>>>> camlp4/Camlp4Printers/Camlp4OCamlAstDumper.cmo
>>>> camlp4/Camlp4Printers/Camlp4OCamlPrinter.cmo
>>>> camlp4/Camlp4Printers/Camlp4OCamlRevisedPrinter.cmo
>>>> camlp4/Camlp4Filters/Camlp4AstLifter.cmo
>>>> camlp4/Camlp4Filters/Camlp4ExceptionTracer.cmo
>>>> camlp4/Camlp4Filters/Camlp4FoldGenerator.cmo
>>>> camlp4/Camlp4Filters/Camlp4LocationStripper.cmo
>>>> camlp4/Camlp4Filters/Camlp4MapGenerator.cmo
>>>> camlp4/Camlp4Filters/Camlp4MetaGenerator.cmo
>>>> camlp4/Camlp4Filters/Camlp4Profiler.cmo
>>>> camlp4/Camlp4Filters/Camlp4TrashRemover.cmo
>>>> # make: *** [byte] Error 10
>>>>
>>>>
>>>>
>>>> =-=- Error report
>>>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>>>> The following actions failed
>>>>     ∗  install camlp4 4.02.0-1modular-implicits
>>>> No changes have been performed
>>>>
>>>>
>>>>
>>>>
>>>> On 03/27/2016 11:48 PM, Mohamed Iguernlala wrote:
>>>>
>>>> Hi,
>>>>
>>>> I guess "pkg-config" is not installed on your system. Can you confirm
>>>> that by just trying "pkg-config --help" in a terminal ?
>>>>
>>>> Regards,
>>>> Mohamed.
>>>>
>>>>
>>
>> --
>> 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


  reply	other threads:[~2016-03-28 13:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-28  3:08 Helmut Brandl
2016-03-28  5:48 ` Mohamed Iguernlala
2016-03-28 12:32   ` Helmut Brandl
2016-03-28 12:37     ` Kakadu
2016-03-28 12:44       ` Helmut Brandl
2016-03-28 12:51         ` Kakadu
2016-03-28 13:14           ` Helmut Brandl [this message]
     [not found]             ` <56F930FF.6080607@inria.fr>
2016-03-28 13:36               ` Helmut Brandl
2016-03-28 13:40             ` Kakadu
2016-03-28 14:13               ` Helmut Brandl
     [not found]                 ` <56F94198.1040505@inria.fr>
2016-03-28 14:58                   ` Helmut Brandl
2016-03-28 11:12 ` Mr. Herr
2016-03-28 12:13   ` Francois Berenger
2016-03-28 12:27     ` Helmut Brandl

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=56F92E18.9000401@gmx.net \
    --to=helmut.brandl@gmx.net \
    --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).