Very weird runtime error

40 views
Skip to first unread message

Robert Krawitz

unread,
Feb 5, 2016, 8:00:33 PM2/5/16
to hugi...@googlegroups.com
I'm getting a rather strange runtime error. Running openSUSE Leap
42.1, building my own package from hg:

$ /usr/bin/hugin
Fatal Error: Mismatch between the program and library build versions detected.
The library used 2.8 (no debug,Unicode,compiler with C++ ABI 1002,STL containers,compatible with 2.6),
and your program used 2.8 (no debug,Unicode,compiler with C++ ABI 1009,STL containers,compatible with 2.6).
Aborted

--
Robert Krawitz <r...@alum.mit.edu>

*** MIT Engineers A Proud Tradition http://mitathletics.com ***
Member of the League for Programming Freedom -- http://ProgFree.org
Project lead for Gutenprint -- http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton

Greg 'groggy' Lehey

unread,
Feb 5, 2016, 8:04:27 PM2/5/16
to hugi...@googlegroups.com
On Friday, 5 February 2016 at 19:59:45 -0500, Robert Krawitz wrote:
> I'm getting a rather strange runtime error. Running openSUSE Leap
> 42.1, building my own package from hg:
>
> $ /usr/bin/hugin
> Fatal Error: Mismatch between the program and library build versions detected.
> The library used 2.8 (no debug,Unicode,compiler with C++ ABI 1002,STL containers,compatible with 2.6),
> and your program used 2.8 (no debug,Unicode,compiler with C++ ABI 1009,STL containers,compatible with 2.6).
> Aborted

I would have thought that that error message is particularly clear,
modulo mentioning the name of the library. Do you need help moving
between ABI versions?

Greg
--
Sent from my desktop computer.
Finger gr...@FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua
signature.asc

Robert Krawitz

unread,
Feb 5, 2016, 8:14:40 PM2/5/16
to hugi...@googlegroups.com, hugi...@googlegroups.com
On Sat, 6 Feb 2016 12:04:22 +1100, Greg 'groggy' Lehey wrote:
> On Friday, 5 February 2016 at 19:59:45 -0500, Robert Krawitz wrote:
>> I'm getting a rather strange runtime error. Running openSUSE Leap
>> 42.1, building my own package from hg:
>>
>> $ /usr/bin/hugin
>> Fatal Error: Mismatch between the program and library build versions detected.
>> The library used 2.8 (no debug,Unicode,compiler with C++ ABI 1002,STL containers,compatible with 2.6),
>> and your program used 2.8 (no debug,Unicode,compiler with C++ ABI 1009,STL containers,compatible with 2.6).
>> Aborted
>
> I would have thought that that error message is particularly clear,
> modulo mentioning the name of the library. Do you need help moving
> between ABI versions?

ABI versions of what?

Jan Dubiec

unread,
Feb 6, 2016, 2:20:19 AM2/6/16
to hugi...@googlegroups.com
On 2016-02-06 02:13, Robert Krawitz wrote:
[...]
> ABI versions of what?
Compilers ABI, i.e. C++ ABI version 1002 vs. 1009. I bet that you
compile hugin with gcc 5.2/5.3 and have wxWidgets compiled with gcc 4.x.

http://stackoverflow.com/questions/23895081/can-you-mix-c-compiled-with-different-versions-of-the-same-compiler.

Robert Krawitz

unread,
Feb 6, 2016, 11:45:40 AM2/6/16
to hugi...@googlegroups.com, hugi...@googlegroups.com
On Sat, 6 Feb 2016 08:19:55 +0100, Jan Dubiec wrote:
> On 2016-02-06 02:13, Robert Krawitz wrote:
> [...]
>> ABI versions of what?
> Compilers ABI, i.e. C++ ABI version 1002 vs. 1009. I bet that you
> compile hugin with gcc 5.2/5.3 and have wxWidgets compiled with gcc 4.x.

I thought of that. I *thought* that I recompiled it with 4.x, but
still see that problem. I'll take another shot at it.

> http://stackoverflow.com/questions/23895081/can-you-mix-c-compiled-with-different-versions-of-the-same-compiler.

Robert Krawitz

unread,
Feb 6, 2016, 10:27:58 PM2/6/16
to hugi...@googlegroups.com, hugi...@googlegroups.com
On Sat, 6 Feb 2016 08:19:55 +0100, Jan Dubiec wrote:
That did turn out to be the issue. I thought I had cleaned up my
build directory, but apparently not. Blowing away my build directory
and recreating it solved it. Sorry for the trouble.
Reply all
Reply to author
Forward
0 new messages