From: julia.lawall@lip6.fr (Julia Lawall)
To: cocci@systeme.lip6.fr
Subject: [Cocci] 1.0.0-rc16: Further fine-tuning for the build system?
Date: Mon, 4 Mar 2013 16:47:44 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.02.1303041645030.1984@hadrien> (raw)
In-Reply-To: <5134C06D.4070906@users.sourceforge.net>
On Mon, 4 Mar 2013, SF Markus Elfring wrote:
> > I don't know what strategy ocamlfind follows, in detail. Perhaps it would be
> > more reasonable to take up the problem with them, since it is a general problem?
>
> I have repeated the following command once more.
>
> Sonne:/home/elfring/Projekte/Menhir/20130116 # make -j6 PREFIX=/usr/local install
>
>
> Now I get an expected result.
>
> elfring at Sonne:~/Projekte/Coccinelle/Bau> ocamlfind query menhirLib
> /usr/lib64/ocaml/site-lib/menhirLib
>
>
> It seems that I was affected by a "questionable" installation order. I am
> curious on improvements also for this software library.
> http://pauillac.inria.fr/~fpottier/menhir/
>
> Does it eventually need better configuration checks?
My impression is that the menhir developers have very few or no resources
to devote to the project now, so probably they are not interested in
making any improvements in this direction.
> But I notice another surprise.
>
> elfring at Sonne:~/Projekte/Coccinelle/Bau> ../lokal/configure --enable-opt
> --enable-ocaml --enable-python --enable-release
> configure: loading site script /usr/share/site/x86_64-unknown-linux-gnu
> configure: configuring coccinelle 1.0.0-rc15 in
> /home/elfring/Projekte/Coccinelle/Bau
> ...
> checking for OCaml findlib package menhirLib... found
> configure: verifying optional features
> checking for menhir... /usr/local/bin/menhir
> ...
> checking python version... 2.7 found
> configure: python major version: 2
> configure: looking for the corresponding python library
> checking for PYTHON... no
> ../lokal/configure: line 15081:
> /home/elfring/Projekte/Coccinelle/Bau/setup/fake-subst.sh: No such file or directory
> configure: error: the python scripts feature is enabled but the pkg-config
> python library is not found
>
>
> How should this error message be resolved?
> https://github.com/coccinelle/coccinelle/issues/9
Maybe you have python but not the developer libraries?
julia
next prev parent reply other threads:[~2013-03-04 15:47 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-02 21:02 [Cocci] 1.0.0-rc16: Further fine-tuning for the build system? SF Markus Elfring
2013-03-02 21:18 ` Julia Lawall
2013-03-04 11:35 ` SF Markus Elfring
2013-03-04 12:36 ` Julia Lawall
2013-03-04 12:37 ` Julia Lawall
2013-03-04 12:43 ` SF Markus Elfring
2013-03-04 12:48 ` Julia Lawall
2013-03-04 13:14 ` SF Markus Elfring
2013-03-04 13:54 ` SF Markus Elfring
2013-03-04 15:40 ` SF Markus Elfring
2013-03-04 15:47 ` Julia Lawall [this message]
2013-03-04 16:05 ` SF Markus Elfring
2013-03-05 8:36 ` Arie Middelkoop
2013-03-07 15:54 ` SF Markus Elfring
2013-03-07 16:27 ` Arie Middelkoop
2013-03-07 17:07 ` SF Markus Elfring
2013-03-16 20:07 ` SF Markus Elfring
2013-03-17 12:18 ` Arie Middelkoop
2013-03-18 9:50 ` SF Markus Elfring
2013-04-07 10:51 ` [Cocci] 1.0.0-rc17: " SF Markus Elfring
2013-04-07 11:05 ` Julia Lawall
2013-04-07 11:14 ` SF Markus Elfring
2013-04-07 11:20 ` Julia Lawall
2013-04-07 11:30 ` SF Markus Elfring
2013-04-07 11:43 ` Julia Lawall
2013-04-07 12:07 ` SF Markus Elfring
2013-04-07 12:11 ` Julia Lawall
2013-04-07 12:13 ` SF Markus Elfring
2013-04-26 8:14 ` [Cocci] 1.0.0-rc16: " Richard W.M. Jones
2013-04-26 9:10 ` SF Markus Elfring
2013-04-26 9:16 ` Richard W.M. Jones
2013-04-26 9:36 ` SF Markus Elfring
2013-04-26 9:52 ` Richard W.M. Jones
2013-04-26 10:15 ` SF Markus Elfring
2013-04-26 10:25 ` Julia Lawall
2013-04-26 11:03 ` Peter Senna Tschudin
2013-04-26 11:28 ` SF Markus Elfring
2013-04-29 9:52 ` [Cocci] 1.0.0-rc17: " 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=alpine.DEB.2.02.1303041645030.1984@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