Bug 1424923

Summary: frama-c-1.13-7 [kernel] user error: cannot load plug-in 'frama-c-jessie': cannot load module
Product: [Fedora] Fedora Reporter: Anton Kochkov <anton.kochkov>
Component: frama-cAssignee: Jerry James <loganjerry>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: loganjerry, msrader
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: frama-c-1.14-1.fc26 frama-c-1.14-1.fc25 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-01 17:31:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Anton Kochkov 2017-02-20 05:28:55 UTC
After installation of frama-c using 'dnf install frama-c', it returns errors:

$ frama-c
[kernel] user error: cannot load plug-in 'gmp': cannot load module
[kernel] user error: cannot load plug-in 'apron.apron': cannot load module
[kernel] user error: cannot load plug-in 'apron.octMPQ': cannot load module
[kernel] user error: cannot load plug-in 'apron.boxMPQ': cannot load module
[kernel] user error: cannot load plug-in 'apron.polkaMPQ': cannot load module
[kernel] user error: cannot load plug-in 'frama-c-value': cannot load module
[kernel] user error: cannot load plug-in 'frama-c-jessie': cannot load module

Even if I install why-jessie ('dnf install why-jessie'), it still shows the error about jessie:
[kernel] user error: cannot load plug-in 'frama-c-jessie': cannot load module

Version-Release number:

frama-c-1.13-7.fc25
why-jessie-2.36-1.fc25

Comment 1 Jerry James 2017-03-03 21:36:55 UTC
It looks like the modules have some undefined symbols.  I will try to get this fixed ASAP.  Sorry for the trouble.

Comment 2 Jerry James 2017-03-25 18:01:06 UTC
The problem was actually in the ocaml-mlgmpidl package, which has not kept up with changes in ocaml infrastructure.  I have updated it and also updated to the latest version of frama-c, since this breakage means nobody has been using the previous version on Fedora 26 anyway.

Comment 3 Fedora Update System 2017-03-26 00:40:26 UTC
apron-0.9.11-6.1097.svn20160801.fc26, flocq-2.5.2-6.fc26, frama-c-1.14-1.fc26, gappalib-coq-1.3.2-4.fc26, ocaml-mlgmpidl-1.2.1-0.21.20150921.fc26, why-2.38-1.fc26, why3-0.87.3-3.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-7be55a4bd6

Comment 4 Fedora Update System 2017-03-26 02:39:32 UTC
apron-0.9.11-6.1097.svn20160801.fc25, frama-c-1.14-1.fc25, ocaml-mlgmpidl-1.2.1-0.21.20150921.fc25, why-2.38-1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-237df63a79

Comment 5 Anton Kochkov 2017-03-27 06:35:33 UTC
Problem disappeared. Thank you!

Comment 6 Fedora Update System 2017-04-01 17:31:54 UTC
apron-0.9.11-6.1097.svn20160801.fc26, flocq-2.5.2-6.fc26, frama-c-1.14-1.fc26, gappalib-coq-1.3.2-4.fc26, ocaml-mlgmpidl-1.2.1-0.21.20150921.fc26, why-2.38-1.fc26, why3-0.87.3-3.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.

Comment 7 Fedora Update System 2017-04-02 20:53:29 UTC
apron-0.9.11-6.1097.svn20160801.fc25, frama-c-1.14-1.fc25, ocaml-mlgmpidl-1.2.1-0.21.20150921.fc25, why-2.38-1.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.