From: julia.lawall@lip6.fr (Julia Lawall)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Build errors with coccinelle 1.0.0-rc24 on OpenBSD and Linux
Date: Mon, 9 Feb 2015 09:51:13 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.10.1502090949070.6846@hadrien> (raw)
In-Reply-To: <20150209082115.GD1632@pl-59055.rocqadm.inria.fr>
On Mon, 9 Feb 2015, S?bastien Hinderer wrote:
> Dear Douglas,
>
> Thanks a lot for the report.
>
> Doug Hogan (2015/02/08 13:49 -0800):
> > There are two build errors with this release. I think both are due to
> > assuming you have parmap installed rather than using the bundled
> > version.
>
> As far as I know, the way it is supposed to work is rather the
> opposite: the build system is supposed to unconditionnally use the
> bundled version. It is also supposed to ignore an installed version,
> which can of course be considered as not very optimal, but that's how
> the situation is supposed to be currently.
Not at all. The build system is supposed to use the installed version if
one is available.
> > For OpenBSD, I'm running OpenBSD -current with OCaml 4.02.1 (ports).
> > For Linux, I'm running Debian testing with OCaml 4.01.0.
>
> I'm also using Debian testing, just re-downloaded the archive of
> 1.0-rc24 rom Coccinlle's web site, unpacked, ran ./configure and make,
> but onmy system it worked,so I'm unable o reproduce the problem so far.
Perhaps you have Parmap installed?
> > Parmap has a bug that prevents it from building on any OS that doesn't
> > have <mach/threads_policy.h> which includes OpenBSD and Linux. Here's
> > the syntax fix:
Doug, this version has now been fixed on the Parmap side, Thanks again
for the report.
julia
next prev parent reply other threads:[~2015-02-09 8:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-08 21:49 [Cocci] Build errors with coccinelle 1.0.0-rc24 on OpenBSD and Linux Doug Hogan
2015-02-08 21:52 ` Julia Lawall
2015-02-09 8:21 ` Sébastien Hinderer
2015-02-09 8:51 ` Julia Lawall [this message]
2015-02-09 12:58 ` Doug Hogan
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.10.1502090949070.6846@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