From: Victor Gambier <victor.gambier@inria.fr>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: cocci@inria.fr, Olaf Hering <olaf@aepfle.de>
Subject: Re: [cocci] Reconsider software dependencies for PCRE support (with SmPL)
Date: Wed, 21 May 2025 13:58:59 +0200 [thread overview]
Message-ID: <ed4c614b-82da-41c9-bd28-1bd5e57f3b2b@inria.fr> (raw)
In-Reply-To: <fdc8e894-1d4c-4d55-bb5d-12cd0fbceac1@web.de>
I'm thinking the issue is simply due to weird dependency issues that are
documented in the file I mentioned. If you'd like me to help you, please
provide me the information I asked for.
Victor
On 19/05/2025 17:50, Markus Elfring wrote:
>> It depends on your current setup and what you want to achieve, …
> Did you stumble on undesirable understanding difficulties?
>
>
>> … and the output of `spatch --version`.
> I informed you that also this program call variant can not work any more
> with my Linux software distribution because the library for PCRE1 became outdated
> and the corresponding package vanished therefore.
>
> * I assume that the usage of regular expressions might not be required for some
> command variants.
>
> * The program can eventually be built without PCRE support (for a while).
>
> * Olaf Hering showed how the PCRE2 support could be activated.
> https://lore.kernel.org/cocci/20250319083051.2862-1-olaf@aepfle.de/
> https://sympa.inria.fr/sympa/arc/cocci/2025-03/msg00161.html
>
>
> Regards,
> Markus
next prev parent reply other threads:[~2025-05-21 11:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-18 8:50 [cocci] Reconsider software dependencies for PCRE support (with SmPL) Markus Elfring
2025-05-18 8:56 ` Julia Lawall
2025-05-19 9:44 ` Victor Gambier
2025-05-19 15:50 ` Markus Elfring
2025-05-21 11:56 ` Markus Elfring
2025-05-21 12:14 ` Olaf Hering
2025-05-21 12:24 ` Markus Elfring
2025-05-21 11:58 ` Victor Gambier [this message]
2025-05-21 12:18 ` Markus Elfring
2025-05-22 6:46 ` 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=ed4c614b-82da-41c9-bd28-1bd5e57f3b2b@inria.fr \
--to=victor.gambier@inria.fr \
--cc=Markus.Elfring@web.de \
--cc=cocci@inria.fr \
--cc=olaf@aepfle.de \
/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).