Bug 21861 - can't run codeblocks (Mismatch between the program and library build versions detected.) [
Summary: can't run codeblocks (Mismatch between the program and library build versions...
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Cesar Vargas
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-14 10:20 CEST by Bernard SIAUD
Modified: 2017-10-27 19:58 CEST (History)
2 users (show)

See Also:
Source RPM: codeblocks-16.01-2.mga7.src.rpm
CVE:
Status comment:


Attachments

Description Bernard SIAUD 2017-10-14 10:20:00 CEST
[troumad@localhost perso]$ codeblocks
Fatal Error: Mismatch between the program and library build versions detected.
The library used 2.8 (no debug,Unicode,compiler with C++ ABI 1011,wx containers,compatible with 2.6),
and your program used 2.8 (no debug,Unicode,compiler with C++ ABI 1009,wx containers,compatible with 2.6).
Abandon (core dumped)
Comment 1 Marja Van Waes 2017-10-14 12:32:44 CEST
Can "compiler with C++ ABI 1011" vs "compiler with C++ ABI 1009" cause this?

Assigning to the registered maintainer.

Summary: can't run => can't run codeblocks (Mismatch between the program and library build versions detected.) [
CC: (none) => marja11
Assignee: bugsquad => cvargas

Comment 2 David Walser 2017-10-18 23:20:53 CEST
Is the maintainer still active?  David was the last one to update it, so I CC'd him.  Maybe it just needs to be rebuilt?

CC: (none) => geiger.david68210

Comment 3 David GEIGER 2017-10-19 18:20:27 CEST
Should be fixed in next codeblocks update:

- codeblocks-16.01-3.mga7
Comment 4 Marja Van Waes 2017-10-27 19:58:54 CEST
Mass-change status to NEW for all bugs that were filed as UNCONFIRMED between October 9 and now, and that still have that status now.

From now on all newly filed bugs will have the NEW status again, like before, regardless of who files the report.

Ever confirmed: 0 => 1
Status: UNCONFIRMED => NEW


Note You need to log in before you can comment on or make changes to this bug.