From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: Jean-Marc Alliot <jean-marc.alliot@irit.fr>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] fftw3 installation fails with opam 1.2.2 and ocaml 4.06.0
Date: Fri, 17 Nov 2017 10:30:57 +0100 [thread overview]
Message-ID: <CAPFanBFwHdg6K3qYPmJQRmo0vobPsEO6NmSO8_xey1fz7o-trw@mail.gmail.com> (raw)
In-Reply-To: <db4e028f-09b6-5bbb-16ba-db2508946e26@irit.fr>
Hi Jean-Marc,
I think that for this kind of issues, opening a ticket on the
bug-tracker of the project is more appropriate than a thread on
caml-list.
I opened an issue there, where I propose that we continue the discussion:
https://github.com/FFTW/fftw3/issues/115
Cheers
On Fri, Nov 17, 2017 at 10:20 AM, Jean-Marc Alliot
<jean-marc.alliot@irit.fr> wrote:
> Well the subject says it all... Hope the following trace will help the
> developpers. After switching back to 4.05.0, installation runs without any
> problem.
>
> Jean-Marc
>
>
> #=== ERROR while installing fftw3.0.7.3
> =======================================#
> # opam-version 1.2.2
> # os linux
> # command make
> # path /home/alliot/.opam/4.06.0/build/fftw3.0.7.3
> # compiler 4.06.0
> # exit-code 2
> # env-file
> /home/alliot/.opam/4.06.0/build/fftw3.0.7.3/fftw3-13606-d2c37b.env
> # stdout-file
> /home/alliot/.opam/4.06.0/build/fftw3.0.7.3/fftw3-13606-d2c37b.out
> # stderr-file
> /home/alliot/.opam/4.06.0/build/fftw3.0.7.3/fftw3-13606-d2c37b.err
> ### stdout ###
> # [...]
> # /home/alliot/.opam/4.06.0/bin/ocamldep fftw3_geomC.ml > ._d/fftw3_geomC.d
> # /home/alliot/.opam/4.06.0/bin/ocamldep fftw3_utils.ml > ._d/fftw3_utils.d
> # /home/alliot/.opam/4.06.0/bin/ocamlc.opt -c -cc "cc" -ccopt "-fPIC -g -O2
> -DFFTW3F_EXISTS -DHASH_EXISTS \
> # -DPIC \
> # -o fftw3_stubs.o " fftw3_stubs.c
> # ../OCamlMakefile:1124 : la recette pour la cible « fftw3_stubs.o » a
> échouée
> # make[2] : on quitte le répertoire «
> /home/alliot/.opam/4.06.0/build/fftw3.0.7.3/src »
> # ../OCamlMakefile:784 : la recette pour la cible « byte-code-library » a
> échouée
> # make[1] : on quitte le répertoire «
> /home/alliot/.opam/4.06.0/build/fftw3.0.7.3/src »
> # Makefile:19 : la recette pour la cible « all » a échouée
> ### stderr ###
> # [...]
> # bigarray_stubs.c:21:16: error: static declaration of ‘caml_ba_num_elts’
> follows non-static declaration
> # static uintnat caml_ba_num_elts(struct caml_ba_array * b)
> # ^~~~~~~~~~~~~~~~
> # In file included from fftw3_stubs.c:32:0:
> # /home/alliot/.opam/4.06.0/lib/ocaml/caml/bigarray.h:117:20: note: previous
> declaration of ‘caml_ba_num_elts’ was here
> # CAMLextern uintnat caml_ba_num_elts(struct caml_ba_array * b);
> # ^~~~~~~~~~~~~~~~
> # make[2]: *** [fftw3_stubs.o] Erreur 2
> # make[1]: *** [byte-code-library] Erreur 2
> # make: *** [all] Erreur 2
>
>
> --
> 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
prev parent reply other threads:[~2017-11-17 9:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 9:20 Jean-Marc Alliot
2017-11-17 9:30 ` Gabriel Scherer [this message]
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=CAPFanBFwHdg6K3qYPmJQRmo0vobPsEO6NmSO8_xey1fz7o-trw@mail.gmail.com \
--to=gabriel.scherer@gmail.com \
--cc=caml-list@inria.fr \
--cc=jean-marc.alliot@irit.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