From: Arend van Spriel <arend@broadcom.com>
To: "backports@vger.kernel.org" <backports@vger.kernel.org>
Subject: how to deal with coccinelle version requirements
Date: Thu, 4 Jun 2015 11:19:45 +0200 [thread overview]
Message-ID: <55701831.20700@broadcom.com> (raw)
I am running a build server on Ubuntu 14.04 and recently had to upgrade
coccinelle for backports builds. So I got my hands on a debian package
(from launchpad if I recall correctly) and installing it manually gives
me following warning:
$ sudo dpkg -i coccinelle_1.0.0~rc24.deb-1_amd64.deb
Selecting previously unselected package coccinelle.
(Reading database ... 309776 files and directories currently installed.)
Preparing to unpack coccinelle_1.0.0~rc24.deb-1_amd64.deb ...
Unpacking coccinelle (1.0.0~rc24.deb-1) ...
dpkg: dependency problems prevent configuration of coccinelle:
coccinelle depends on libpcre3 (>= 1:8.35); however:
Version of libpcre3:amd64 on system is 1:8.31-2ubuntu2.
dpkg: error processing package coccinelle (--install):
dependency problems - leaving unconfigured
Processing triggers for man-db (2.6.7.1-1) ...
Errors were encountered while processing:
coccinelle
Now spatch is installed and works just fine, but I am getting all kinds
of errors when trying to install other packages which kinda sucks. So I
tried unstalling coccinelle and just build it from github repo, but that
fails for me as well (giving 'Unbound module Pcre').
So can anyone recommend a way to deal with the coccinelle version
requirements when running on Ubuntu LTS version.
Regards,
Arend
next reply other threads:[~2015-06-04 9:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 9:19 Arend van Spriel [this message]
2015-06-04 9:24 ` how to deal with coccinelle version requirements Hauke Mehrtens
2015-06-04 9:46 ` Arend van Spriel
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=55701831.20700@broadcom.com \
--to=arend@broadcom.com \
--cc=backports@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.