octave-maintainers
[Top][All Lists]
Advanced

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

Re: GraphicsMagick linkage error on Mac OS X 10.9


From: Ben Abbott
Subject: Re: GraphicsMagick linkage error on Mac OS X 10.9
Date: Sat, 11 Jan 2014 18:07:51 -0500

On Jan 11, 2014, at 5:25 PM, Daryl Lee <address@hidden> wrote:

> On Jan 11, 2014, at 3:18 PM, Daryl Lee <address@hidden> wrote:
> 
>> On Jan 11, 2014, at 8:06 AM, Pantxo <address@hidden> wrote:
>> 
>>> I have the exact same issue. I think it may be related to the stdlib against
>>> which graphicsmagick is linked as explained in this thread [1].  Using fink
>>> for dependencies I can see that libc++ is used instead of libstdc++:
>>> $otool -L otool -L /sw/lib/libGraphicsMagick++-Q32.3.dylib
>>> /sw/lib/libGraphicsMagick++-Q32.3.dylib:
>>>     /sw/lib/libGraphicsMagick++-Q32.3.dylib (compatibility version 10.0.0,
>>> current version 10.2.0)
>>>     /sw/lib/libGraphicsMagick-Q32.3.dylib (compatibility version 15.0.0,
>>> current version 15.0.0)
>>>     /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version
>>> 1197.1.1)
>>>     /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version
>>> 120.0.0)
>>> 
>>> If "otool -L" gives you the same result, could you try as suggested in the
>>> thread, to recompile GraphicsMagick using -stdlib=libstdc++ flag.
>>> 
>> 
>> Thanks for the quick response.  I can't find a 
>> 'libGraphicsMagick++-Q32.3.dylib' file anywhere on my system (and I don't 
>> have a /sw directory), so I just assumed your suggestion was correct.  Now 
>> my problem is in implementing it.
>> 
>> In the GraphicsMagick build tree I added --with-stdlib=libstdc++ flag to the 
>> other configuration options and rebuilt GraphicsMagick. Then, when I tried 
>> the same thing building Octave, I got the same linkage errors as before.
>> 
> 
> I don't know if this has anything to do with it, but I just did this:
> 
>  sudo port uninstall GraphicsMagick
> 
> and learned that I have three versions installed: 1.3.18_0+q32, 1.3.18_0_q8, 
> and 1.3.19_0+q32 (active).  Could that have anything to do with what I'm 
> experiencing?

I'm building the developer's sources Mavericks and am using Macports for 
dependencies.  To install most of the dependencies ...

sudo port install octave @3.6.4 +atlas+docs+fltk+gcc48+x11
sudo port deactivate octave
sudo port install GraphicsMagick +q32

To build ...

./bootstrap
./configure                                        \
   CC=/opt/local/bin/gcc-mp-4.8                           \
   CFLAGS="-pipe -O2 -m64"                                \
   CPPFLAGS="-D_THREAD_SAFE -I/opt/local/include"         \
   LDFLAGS="-L/opt/local/lib -m64 "                       \
   CXX=/opt/local/bin/g++-mp-4.8                          \
   CXXFLAGS="-pipe -O2 -m64"                              \
   F77=/opt/local/bin/gfortran-mp-4.8                     \
   FFLAGS="-pipe -O2 -m64"                                \
   LLVM_CONFIG=/opt/local/bin/llvm-config-mp-3.3          \
   --with-lapack="-llapack -latlas -lgfortran"            \
   --with-blas="-lcblas -lf77blas -latlas -lgfortran"     \
   --prefix=/opt/octave/3.7                               \
   --enable-gui                                           \
   --disable-jit                                          \
   --disable-java                                         \
   --with-framework-carbon                                \
   --with-arpack                                          \
   --enable-docs                                          \
   --with-opengl                                          \
   --without-x                                            
make -j4

Ben



reply via email to

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