octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: octave 4.1.0+ w/ clang-3.8


From: Mike Miller
Subject: Re: octave 4.1.0+ w/ clang-3.8
Date: Mon, 20 Jun 2016 09:15:44 -0700
User-agent: Mutt/1.6.0 (2016-04-01)

On Sun, Jun 19, 2016 at 23:36:52 -0500, Dmitri A. Sergatskov wrote:
> It was wrong "T". Anyway I am still not quite sure in what is going on:
> 
> objdump -T libinterp/.libs/liboctinterp.so | grep description
> 0000000000000000      D  *UND*    0000000000000000 
> _ZNK6Magick9CoderInfo11descriptionEv
> 
> 
> objdump -T /usr/lib64/libGraphicsMagick++-Q16.so.12.1.0 | grep description
> 000000000003cca0 g    DF .text    0000000000000023  Base 
> _ZNK6Magick9CoderInfo11descriptionB5cxx11Ev

This looks like the C++11 ABI switch, any time you see a symbol mismatch
with a "cxx11" tag in it. See the GCC page [1] and earlier threads about
this, [2] for example. Basically, make sure all your C++ libraries and
Octave are built with the same C++ ABI. If GraphicsMagick was built with
the new ABI, then Octave also must be built with the new ABI.

[1]: https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dual_abi.html
[2]: http://lists.gnu.org/archive/html/help-octave/2016-02/msg00113.html

-- 
mike



reply via email to

[Prev in Thread] Current Thread [Next in Thread]