From: Roberto Di Cosmo <roberto@dicosmo.org>
To: caml-list@inria.fr
Subject: Re: [Caml-list] parmap package broken in opam switch 4.03.0
Date: Tue, 26 Apr 2016 18:21:43 +0200 [thread overview]
Message-ID: <20160426162143.GA15142@traveler> (raw)
In-Reply-To: <20160426143541.GB21686@pl-59055.rocqadm.inria.fr>
Hi Sebastien,
thanks for reporting this; in principle, it would be better to just open an
issue on https://github.com/rdicosmo/parmap but this seems indeed to be an issue
with 4.03, that may hit other people, so I'm following up here.
The problem is related to setcore.mli, which is just the interface for some C
code, so there is no setcore.ml, hence no setcore.cmx either; compilation of
such cases ran along just fine via ocamlbuild up to 4.02
It seems that in 4.03 one needs to add the -opaque flag when compiling
such stubs, otherwise things go astray, and it seems ocamlbuild does not
detect automatically such situations, so one needs to explicitly pass
the -opaque option when compiling setcore.mli (and only it).
If people on the list can confirm this, we'll then need to adapt parmap's
autoconf / makefile with code that spots whether we are using 4.03+.
If some kind soul wants to lend a hand, it would be much
appreciated... otherwise I'll try to do it in a moment of spare time
all the best
--
Roberto
On Tue, Apr 26, 2016 at 04:35:41PM +0200, Sébastien Hinderer wrote:
> Hi,
>
> It seems the Setcore module is not correctly included in the parmap
> library in opam's 4.03.0 switch:
>
> ~$ ocamlobjinfo .opam/4.03.0/lib/parmap/parmap.cmxa | grep -i setcore
> 7d7337fa605045f3c5ec064376ede776 Setcore
> -------------------------------- Setcore
>
> (where the first line corresponds to the Interfaces imported by the
> Parmap module and the second line to the Implementations imported by that
> same module)
>
> Practically, when one tries to compile a program using parmap, one gets
> an error while trying to link parmap.cmxa about the Setcore symbol which
> is not found.
>
> Sébastien.
>
> --
> 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
--
Roberto Di Cosmo
------------------------------------------------------------------
Professeur (on leave at/detache a INRIA Roquencourt)
IRIF E-mail : roberto@dicosmo.org
Universite Paris Diderot Web : http://www.dicosmo.org
Case 7014 Twitter : http://twitter.com/rdicosmo
5, Rue Thomas Mann
F-75205 Paris Cedex 13 France
------------------------------------------------------------------
Office location:
Paris Diderot INRIA
Bureau 3020 (3rd floor) Bureau C123
Batiment Sophie Germain Batiment C
8 place Aurélie Nemours 2, Rue Simone Iff
Tel: +33 1 57 27 92 20 Tel: +33 1 80 49 44 42
Metro
Bibliotheque F. Mitterrand Ligne 6: Dugommier
ligne 14/RER C Ligne 14/RER A: Gare de Lyon
------------------------------------------------------------------
GPG fingerprint 2931 20CE 3A5A 5390 98EC 8BFC FCCA C3BE 39CB 12D3
next prev parent reply other threads:[~2016-04-26 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 14:35 Sébastien Hinderer
2016-04-26 16:21 ` Roberto Di Cosmo [this message]
2016-04-26 17:16 ` Leo White
2016-04-27 9:49 ` Roberto Di Cosmo
2016-04-27 11:24 ` Sébastien Hinderer
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=20160426162143.GA15142@traveler \
--to=roberto@dicosmo.org \
--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