From: Emilian.Medve@Freescale.com (Emil Medve)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Error: Unbound value Common.union_set
Date: Mon, 5 Jan 2015 16:15:39 -0600 [thread overview]
Message-ID: <54AB0D0B.3030909@Freescale.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1501052253220.2025@localhost6.localdomain6>
Hello Julia,
On 01/05/2015 03:54 PM, Julia Lawall wrote:
> On Mon, 5 Jan 2015, Emil Medve wrote:
>
>> Hello,
>>
>>
>> I'm seeing the following errors:
>>
>>> File "/tmp/ocaml_cocci_cfd8ea.ml", line 21, characters 23-39:
>>> Error: Unbound value Common.union_set
>
> This is really strange. What semantic patch are you running?
All of them as I'm not using COCCI=... to select some specific single
patch. I'll narrow it down a bit and get back to you
> Could you try spatch --sp-file us.cocci us.c
>
> where us.cocci is:
>
> @script:ocaml@
> @@
>
> let _ = Common.union_set [1;2] [3] in
> Printf.printf "ok\n"
>
> @@
> @@
>
> - foo();
>
> and us.c is:
>
> int main () {
> foo();
> }
I'm sure this makes more sense to you then it makes to me:
> $ spatch --sp-file us.cocci us.c
> init_defs_builtins: /usr/lib64/ocaml/coccinelle/standard.h
> Using native version of ocamlc/ocamlopt/ocamldep
> ocamlopt.opt -shared -o /tmp/ocaml_cocci_e217fe.cmxs -g -I /usr/lib64/ocaml -I /usr/lib64/ocaml/coccinelle//ocaml /tmp/ocaml_cocci_e217fe.ml
> File "/tmp/ocaml_cocci_e217fe.ml", line 15, characters 6-36:
> Error: Unbound value Iteration.add_pending_instance
> Fatal error: exception Yes_prepare_ocamlcocci.CompileFailure("/tmp/ocaml_cocci_e217fe.ml")
Cheers,
> thanks,
> julia
>
>>> File "/tmp/ocaml_cocci_0b6504.ml", line 21, characters 23-39:
>>> Error: Unbound value Common.union_set
>>> Fatal error: exception Yes_prepare_ocamlcocci.CompileFailure("/tmp/ocaml_cocci_cfd8ea.ml")
>>> Fatal error: exception Yes_prepare_ocamlcocci.CompileFailure("/tmp/ocaml_cocci_0b6504.ml")
>>> File "/tmp/ocaml_cocci_5c8de6.ml", line 21, characters 23-39:
>>> File "/tmp/ocaml_cocci_bb345d.ml", line 21, characters 23-39:
>>> Error: Unbound value Common.union_set
>>> Error: Unbound value Common.union_set
>>> Fatal error: exception Yes_prepare_ocamlcocci.CompileFailure("/tmp/ocaml_cocci_bb345d.ml")
>>> Fatal error: exception Yes_prepare_ocamlcocci.CompileFailure("/tmp/ocaml_cocci_5c8de6.ml")
>>> File "/tmp/ocaml_cocci_84f1b1.ml", line 21, characters 23-39:
>>> File "/tmp/ocaml_cocci_e0436a.ml", line 21, characters 23-39:
>>> Error: Unbound value Common.union_set
>>> Error: Unbound value Common.union_set
>>> Fatal error: exception Yes_prepare_ocamlcocci.CompileFailure("/tmp/ocaml_cocci_e0436a.ml")
>>> Fatal error: exception Yes_prepare_ocamlcocci.CompileFailure("/tmp/ocaml_cocci_84f1b1.ml")
>>> File "/tmp/ocaml_cocci_f46b5a.ml", line 21, characters 23-39:
>>> Error: Unbound value Common.union_set
>>> Fatal error: exception Yes_prepare_ocamlcocci.CompileFailure("/tmp/ocaml_cocci_f46b5a.ml")
>>> File "/tmp/ocaml_cocci_a89bea.ml", line 21, characters 23-39:
>>> Error: Unbound value Common.union_set
>>> Fatal error: exception Yes_prepare_ocamlcocci.CompileFailure("/tmp/ocaml_cocci_a89bea.ml")
>>
>> Here is the context and a few relevant version numbers:
>>
>>> make coccicheck MODE=report M=...
>>> $ git describe --abbrev=0
>>> v3.19-rc2
>>> $ spatch --version
>>> spatch version 1.0.0-rc23 with Python support and with PCRE support
>>> $ ocaml -version
>>> The OCaml toplevel, version 4.02.1
>>
>> Any advice? Need extra information?
>>
>>
>> Cheers,
>> _______________________________________________
>> Cocci mailing list
>> Cocci at systeme.lip6.fr
>> https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2015-01-05 22:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 21:30 [Cocci] Error: Unbound value Common.union_set Emil Medve
2015-01-05 21:54 ` Julia Lawall
2015-01-05 22:15 ` Emil Medve [this message]
2015-01-05 22:19 ` Julia Lawall
2015-01-05 22:50 ` Emil Medve
2015-01-06 10:09 ` Julia Lawall
2015-01-07 7:30 ` Emil Medve
2015-01-06 15:39 ` 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=54AB0D0B.3030909@Freescale.com \
--to=emilian.medve@freescale.com \
--cc=cocci@systeme.lip6.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.