cocci.inria.fr archive mirror
 help / color / mirror / Atom feed
From: Kaspar Schleiser <kaspar@schleiser.de>
To: Nicolas Palix <nicolas.palix@univ-grenoble-alpes.fr>,
	Julia Lawall <julia.lawall@lip6.fr>,
	cocci@systeme.lip6.fr
Subject: Re: [Cocci] 1.0.8 on Ubuntu
Date: Tue, 5 May 2020 11:16:41 +0200	[thread overview]
Message-ID: <ed125ed8-a2f8-2c1a-b0aa-acf83544cae8@schleiser.de> (raw)
In-Reply-To: <904fcac6-77cb-b44b-07fd-430bf3596614@univ-grenoble-alpes.fr>

Hi Nicolas,

thanks for the quick reply!

On 5/5/20 10:50 AM, Nicolas Palix wrote:
> I think you could try the following version (intended for 20.10).
> https://launchpad.net/ubuntu/+source/coccinelle/1.0.8.deb-2

I managed to compile the 19.04 version
(coccinelle_1.0.8~19.04npalix1.dsc,
coccinelle_1.0.8~19.04npalix1.tar.xz). Somehow I missed that there's a
20.10 version.

The commands were roughly:

$ apt install debhelper devscripts equivs
$ dpkg-source -x coccinelle_1.0.8~19.04npalix1.dsc
$ cd coccinelle-1.0.8
$ mk-build-deps -i
$ dpkg-buildpackage -rfakeroot -b
$ apt install ../coccinelle_1.0.8~19.04npalix1_amd64.deb

The resulting .deb can be installed on an otherwise clean focal:latest
container. The spatch binary starts (prints help), did not do further
testing.

Kaspar
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci

  reply	other threads:[~2020-05-05  9:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-30 19:43 [Cocci] 1.0.8 on Ubuntu Julia Lawall
2020-05-05  8:16 ` Kaspar Schleiser
2020-05-05  8:50   ` Nicolas Palix
2020-05-05  9:16     ` Kaspar Schleiser [this message]
2020-05-05 12:05       ` Nicolas Palix
2020-05-05 13:23         ` Julia Lawall
2020-05-05 13:52           ` kaspar
2020-05-05 19:50           ` Kaspar Schleiser

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=ed125ed8-a2f8-2c1a-b0aa-acf83544cae8@schleiser.de \
    --to=kaspar@schleiser.de \
    --cc=cocci@systeme.lip6.fr \
    --cc=julia.lawall@lip6.fr \
    --cc=nicolas.palix@univ-grenoble-alpes.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).