cocci.inria.fr archive mirror
 help / color / mirror / Atom feed
From: Jan Tojnar <jtojnar@gmail.com>
To: cocci@inria.fr
Cc: Thierry.Martinez@inria.fr
Subject: [cocci] No longer possible to build with system dependencies?
Date: Sat, 22 Oct 2022 11:22:04 +0200	[thread overview]
Message-ID: <e3746c66c0f9c0747620dd7536c98ca6deb5399b.camel@gmail.com> (raw)

Hi,

I tried building Coccinelle from the latest commit from master but it
appears it is no longer possible to do so without relying on bundles.

I like to use libraries from my Linux distribution since then I do not
have to build them over and over again every time I nuke the repo.
Additionally, since distros tend to use sandboxed environment for
building packages, building dependencies independently reduces
excessively long rebuild time when failure occurs higher in the
dependency tree.

Looking at the commit history, the last change to `configure.ac` file
from the following commit is responsible:

https://github.com/coccinelle/coccinelle/commit/1d0733a27006b06eef712f541000a8bf10246804

in addition to:

https://github.com/coccinelle/coccinelle/commit/3f54340c8ac907e528dbe1475a4a7141e77b9cdd

If this was done to prevent people from using old versions of the
libraries, would it be possible to add a minimum version check instead?
Or at least add an option to force the use of system libraries,
so that distros do not have to patch the limitation out to comply with
their policies on packaging vendored dependencies?

Cheers,

Jan

             reply	other threads:[~2022-10-22  9:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-22  9:22 Jan Tojnar [this message]
2022-10-22 10:26 ` [cocci] No longer possible to build with system dependencies? Julia Lawall
2022-10-25 14:54 ` Julia Lawall
2022-10-25 20:35   ` Jan Tojnar
2022-10-25 20:44     ` Julia Lawall
2022-10-26  6:18     ` Markus Elfring
2022-10-26  8:05     ` Thierry Martinez
2022-10-26 11:00       ` Markus Elfring
2022-10-28 18:12       ` Markus Elfring
2022-10-29  7:15       ` [cocci] Checking quotation variants 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=e3746c66c0f9c0747620dd7536c98ca6deb5399b.camel@gmail.com \
    --to=jtojnar@gmail.com \
    --cc=Thierry.Martinez@inria.fr \
    --cc=cocci@inria.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;
as well as URLs for NNTP newsgroup(s).