From: Markus Elfring <Markus.Elfring@web.de>
To: cocci@inria.fr, Thierry Martinez <Thierry.Martinez@inria.fr>,
Julia Lawall <julia.lawall@inria.fr>
Cc: Tommi Rantala <tt.rantala@gmail.com>
Subject: Re: [cocci] Checking the software build dependency “bundles/pcre/pcre-ocaml/src/pcre.ml.in”
Date: Wed, 8 Mar 2023 17:24:38 +0100 [thread overview]
Message-ID: <a999ee84-3e64-c6d8-5aae-13ed5c79a838@web.de> (raw)
In-Reply-To: <a68b1738-568d-1289-9929-51687b06941e@web.de>
[-- Attachment #1: Type: text/plain, Size: 861 bytes --]
> Markus_Elfring@Sonne:…/Projekte/Coccinelle/20160205> git pull && make distclean &&./autogen && ./configure
>
> …
> configure: creating ./config.status
> config.status: error: cannot find input file: `bundles/pcre/pcre-ocaml/src/pcre.ml.in'
>
I got the impression that the following part of the build specification needs
to be reconsidered somehow.
https://gitlab.inria.fr/coccinelle/coccinelle/-/blob/8e007c83bbf35ace2f879b790e24057e39053c01/configure.ac#L570
…
AC_CONFIG_FILES([
bundles/pcre/pcre-ocaml/src/pcre.ml
bundles/pcre/pcre-ocaml/src/pcre_stubs.c
])])
…
We are also waiting on further information for the topic “Support for PCRE2”.
https://lore.kernel.org/cocci/alpine.DEB.2.22.394.2207222129160.2321@hadrien/
https://sympa.inria.fr/sympa/arc/cocci/2022-07/msg00027.html
Regards,
Markus
[-- Attachment #2: Type: text/html, Size: 3306 bytes --]
prev parent reply other threads:[~2023-03-08 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 10:49 [cocci] [PATCH] Fix find -name flag when combining --c++ and --include-headers Tommi Rantala
2023-03-07 11:12 ` Julia Lawall
2023-03-07 11:14 ` Julia Lawall
2023-03-08 10:05 ` [cocci] Checking the software build dependency “bundles/pcre/pcre-ocaml/src/pcre.ml.in” Markus Elfring
2023-03-08 16:24 ` Markus Elfring [this message]
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=a999ee84-3e64-c6d8-5aae-13ed5c79a838@web.de \
--to=markus.elfring@web.de \
--cc=Thierry.Martinez@inria.fr \
--cc=cocci@inria.fr \
--cc=julia.lawall@inria.fr \
--cc=tt.rantala@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).