[Octave-bug-tracker] [bug #54235] problems building Octave on Solaris

[Mike Miller]

Follow-up Comment #62, bug #54235 (project octave):

It's possible that the GraphicsMagick undefined symbols is related to the GCC
ABI change that happened around the release of GCC 5.1.

I don't know if there is a Solaris objdump command or equivalent, but this is
how I would check for this on GNU/Linux


$ objdump -T /usr/lib/libGraphicsMagick++.so | grep _ZN6Magick9CoderInfoC1ERK
$ objdump -T ./libinterp/.libs/liboctinterp.so | grep
_ZN6Magick9CoderInfoC1ERK


and see whether the results match.

If the symbol is '_ZN6Magick9CoderInfoC1ERKSs', then it was built with the old
C++98 ABI naming convention.

If the symbol is
'_ZN6Magick9CoderInfoC1ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE',
then it was built with the new C++11 ABI naming convention.

If the GraphicsMagick library contains the new naming scheme, then I don't
think it is possible to link Octave against GraphicsMagick using GCC 4.9.2,
you will have to drop GraphicsMagick, recompile it yourself using GCC 4.9.2,
or try using GCC 5 again.

And all of this may or may not be related to the "multiple inclusion" warning,
which may or may not be a fatal problem once we get past this problem.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?54235>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/