From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Build configuration challenges around "Menhir"
Date: Wed, 18 May 2016 10:28:49 +0200 [thread overview]
Message-ID: <a3fa0af3-b679-124d-09c3-60385e6ad34f@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1605180711280.2031@localhost6.localdomain6>
>> error: the file parser_cocci_menhir.ml is needed, which requires
>> preprocessing by menhir to obtain it from parser_cocci_menhir.mly.
>> However, menhir is not enabled.
>
> Indeed, it is not there. I guess it was decided that people who use
> github should have the capability to generate everything from scratch.
> But I don't really know... Will check.
Are there a few build challenges left over for proper configuration checks
around the bundling (or other source) of this software library?
https://github.com/coccinelle/coccinelle/blob/cd539cd12ad0674d5a8f4c33f6c21ae00aec8e57/configure.ac#L152
https://github.com/coccinelle/coccinelle/blob/db45d7549bdde52f95bf2885ef652a42862854bb/setup/fake-menhir.sh#L5
Regards,
Markus
next prev parent reply other threads:[~2016-05-18 8:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 17:20 [Cocci] compiling latest coccinelle on opensuse Luis R. Rodriguez
2016-05-17 20:52 ` Julia Lawall
2016-05-17 22:44 ` Luis R. Rodriguez
2016-05-18 5:12 ` Julia Lawall
2016-05-18 8:28 ` SF Markus Elfring [this message]
2016-05-18 8:43 ` [Cocci] Build configuration challenges around "Menhir" Julia Lawall
2016-05-18 8:48 ` SF Markus Elfring
2016-05-18 9:08 ` Julia Lawall
2016-05-18 9:22 ` SF Markus Elfring
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=a3fa0af3-b679-124d-09c3-60385e6ad34f@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--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.