cocci.inria.fr archive mirror
 help / color / mirror / Atom feed
From: timur@kernel.org (Timur Tabi)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Problem with improper multi-line string literals
Date: Mon, 15 Oct 2018 13:35:35 -0500	[thread overview]
Message-ID: <CAOZdJXXg+su+OXjb15wnpwk1WNZY-MyVAE8oZxwRud2pgGOQyw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1810151853140.10109@hadrien>

On Mon, Oct 15, 2018 at 11:55 AM Julia Lawall <julia.lawall@lip6.fr> wrote:
> Do you have parmap installed on your machine?  Try
>
> ocamlfind query parmap

$  ocamlfind query parmap
/usr/lib/ocaml/parmap

> Then try which ocaml and see if they have the same prefix.  For example,
> I have:
>
> hadrien: ocamlfind query parmap
> /home/jll/.opam/4.06.1/lib/parmap
> hadrien: which ocaml
> /home/jll/.opam/4.06.1/bin/ocaml

$ which ocaml
/usr/bin/ocaml
$ ocaml --version
The OCaml toplevel, version 4.05.0

I have a stock Ubuntu 18.04 installation.

  reply	other threads:[~2018-10-15 18:35 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 [this message]
2018-10-16 15:10     ` Himanshu Jha
2018-10-16 15:12       ` Julia Lawall
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=CAOZdJXXg+su+OXjb15wnpwk1WNZY-MyVAE8oZxwRud2pgGOQyw@mail.gmail.com \
    --to=timur@kernel.org \
    --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).