Search Criteria
Package Details: coccinelle 1.1.1-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/coccinelle.git (read-only, click to copy) |
---|---|
Package Base: | coccinelle |
Description: | Provides spatch program used to apply semantic patches |
Upstream URL: | http://coccinelle.lip6.fr/ |
Licenses: | GPL2 |
Submitter: | hsyl20 |
Maintainer: | osandov |
Last Packager: | osandov |
Votes: | 19 |
Popularity: | 0.147555 |
First Submitted: | 2010-03-26 18:18 (UTC) |
Last Updated: | 2022-08-10 17:45 (UTC) |
Latest Comments
1 2 3 4 5 6 7 Next › Last »
osandov commented on 2023-07-05 15:58 (UTC)
@JohnTh the patch doesn't apply cleanly to 1.1.1. If you or someone else can backport it and test it, I can add it to this package, but otherwise you may need to use coccinelle-git instead.
JohnTh commented on 2023-07-01 18:04 (UTC)
I ran into a problem during configure when building coccinelle due to ocaml 5.0. I saw a commit upstream for this, but did not test it: https://github.com/coccinelle/coccinelle/commit/1d0733a27006b06eef712f541000a8bf10246804.patch Cheers
jhubbard commented on 2022-08-10 20:01 (UTC)
The updated version is working perfectly. I've tested it by running the following within today's git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git tree:
make J=20 coccicheck
Thanks, osandov and jkl820, for getting Arch + coccinelle back in fully working order!
osandov commented on 2022-08-10 17:46 (UTC)
@jhubbard thanks for the instructions on how to reproduce this. I added a patch for the upstream fix, which seemed to do the trick for me. Let me know if you still have problems.
jhubbard commented on 2022-08-04 00:46 (UTC)
OK, thanks for pointing out that it is fixed upstream!
@osandov, are you still maintaining this package? (If not, is there someone who wants to jump in?)
jkl820 commented on 2022-08-04 00:04 (UTC)
@jhubbard looks like the issue was fixed here: https://gitlab.inria.fr/coccinelle/coccinelle/-/merge_requests/166
There was no release since then so using the coccinelle-git package instead works well for now.
jhubbard commented on 2022-01-20 00:15 (UTC)
Can anyone help with my previous post? It seems like a real installation bug. Thanks in advance!
jhubbard commented on 2022-01-09 03:44 (UTC)
Hi, I'm seeing an installation problem that only shows up when a cocci script actually uses OCAML (@script:ocaml@). It looks like this (as you might guess, this is from running, approximately, "make coccicheck" in today's Linux kernel tree):
/bin/spatch -D report --no-show-diff --very-quiet --cocci-file ./scripts/coccinelle/api/check_bq27xxx_data.cocci --patch . --dir mm -I ./arch/x86/include -I ./arch/x86/include/generated -I ./include -I ./arch/x86/include/uapi -I ./arch/x86/include/generated/uapi -I ./include/uapi -I ./include/generated/uapi --include ./include/linux/compiler-version.h --include ./include/linux/kconfig.h --jobs 42 --chunksize 1 Fatal error: exception Coccinelle_modules.Yes_prepare_ocamlcocci.CompileFailure("No coccilib.cmi in /usr/bin/lib/coccinelle/ocaml/coccilib.cmi or /usr/bin/lib/coccinelle/ocaml/coccilib/coccilib.cmi") coccicheck failed
...and as you can see, OCAML is incorrectly looking for coccinelle support in /usr/bin/lib/coccinelle (which is a completely invalid place in all cases!). It should be looking in /usr/lib/coccinelle .
I'm using the latest version of coccinelle from this site:
$ spatch --version spatch version 1.1.1 compiled with OCaml version 4.13.1 Flags passed to the configure script: --prefix=/usr --enable-release=yes --with-python=/usr/bin/python3 OCaml scripting support: yes Python scripting support: yes Syntax of regular expressions: PCRE
osandov commented on 2021-01-04 19:28 (UTC)
@oriba I can't reproduce that error. How did you build the package?
oriba commented on 2020-12-05 20:56 (UTC)
Package can't be built:
File "parsing_cocci/parser_cocci_menhir.mli", line 234, characters 25-36: 234 | (Ast_cocci.meta_name * Ast.metavar) option * Ast.mvinit) ^^^^^^^^^^^ Error: Unbound module Ast make: *** [Makefile:426: parsing_cocci/parser_cocci_menhir.cmi] Error 2 ==> ERROR: A failure occurred in build(). Aborting...
1 2 3 4 5 6 7 Next › Last »