From: julia.lawall@lip6.fr (Julia Lawall)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Problem with improper multi-line string literals
Date: Tue, 16 Oct 2018 17:12:04 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1810161711210.3512@hadrien> (raw)
In-Reply-To: <20181016151052.GA26422@himanshu-Vostro-3559>
On Tue, 16 Oct 2018, Himanshu Jha wrote:
> On Mon, Oct 15, 2018 at 11:37:00AM -0500, Timur Tabi wrote:
> > On Sat, Oct 13, 2018 at 4:19 PM Julia Lawall <julia.lawall@lip6.fr> wrote:
> > > This problem has been fixed. Actually, it thought that " of multiline " was the new amount to indent...
> >
> > When I try to build this on Ubuntu 18, I get the following error:
> >
> > OCAMLOPT parsing_c/includes.ml
> > File "parsing_c/includes.ml", line 159, characters 9-22:
> > Error: Unbound module Parmap
> > Makefile:424: recipe for target 'parsing_c/includes.cmx' failed
> > make: *** [parsing_c/includes.cmx] Error 2
> > rm parsing_cocci/lexer_cli.ml parsing_cocci/parser_cocci_menhir.ml.d
> > parsing_cocci/parser_cocci_menhir.mli.d parsing_cocci/lexer_script.ml
> > parsing_cocci/lexer_cocci.ml
> >
> > I installed all the packages listed in install.txt.
> >
> > I tried "./configure --disable-pcre-syntax" and "./configure
> > --disable-ocaml", but neither helped.
>
> FYI coccinelle works fine on Ubuntu 18.04.1 when built through
> source code.
>
> There might be problem for the specific config you're targeting.
> But I'm curious as to how disabling pcre-syntax helps ?
>
> I do understand the purpose of disabling ocaml scripting.
No, disabling OCaml scripting doesn't help either. Parmap is for
parallelism, whether one has OCaml scripting or not.
julia
>
> himanshu at himanshu-Vostro-3559:~$ spatch --version
> spatch version 1.0.7-00498-g41ec93a2 compiled with OCaml version 4.05.0
> Flags passed to the configure script: --with-bash-completion=/etc/bash_completion.d/
> OCaml scripting support: yes
> Python scripting support: yes
> Syntax of regular expresssions: PCRE
>
>
> Thanks
> --
> Himanshu Jha
> Undergraduate Student
> Department of Electronics & Communication
> Guru Tegh Bahadur Institute of Technology
>
next prev parent reply other threads:[~2018-10-16 15:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 21:28 [Cocci] Problem with improper multi-line string literals Timur Tabi
2018-10-12 21:37 ` Julia Lawall
2018-10-12 21:42 ` Timur Tabi
2018-10-12 22:24 ` Timur Tabi
2018-10-12 23:08 ` Timur Tabi
2018-10-12 23:22 ` Timur Tabi
2018-10-13 3:08 ` Julia Lawall
[not found] ` <e4e5dc37-c364-c53d-26f6-52205cfee304@users.sourceforge.net>
2018-10-13 15:56 ` Timur Tabi
2018-10-13 21:19 ` Julia Lawall
2018-10-15 16:37 ` Timur Tabi
2018-10-15 16:39 ` Julia Lawall
2018-10-15 16:50 ` Timur Tabi
2018-10-15 16:55 ` Julia Lawall
2018-10-15 18:35 ` Timur Tabi
2018-10-16 15:10 ` Himanshu Jha
2018-10-16 15:12 ` Julia Lawall [this message]
2018-10-16 16:28 ` Timur Tabi
2018-10-16 16:39 ` Julia Lawall
2018-10-16 17:14 ` Timur Tabi
2018-10-16 17:10 ` Himanshu Jha
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=alpine.DEB.2.20.1810161711210.3512@hadrien \
--to=julia.lawall@lip6.fr \
--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 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).