Issue #37 closed

Ubuntu: error: 'GrayChannel' is not a member of 'Magick'

Ondřej Čertík
created an issue

I am using pgmagick 0.5.6 and graphicsmagick 1.3.18.

[pgmagick] gcc -pthread -fno-strict-aliasing -I/usr/include/x86_64-linux-gnu -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/auto/nest/nest/u/ondrej/repos/python-hpcmp2/opt/python/mdo3/include/python2.7 -I/usr/include/ImageMagick/ -I/auto/nest/nest/u/ondrej/repos/python-hpcmp2/opt/python/mdo3/include/python2.7 -c ./src/_ChannelType.cpp -o build/temp.linux-x86_64-2.7/./src/_ChannelType.o -DPGMAGICK_LIB_GRAPHICSMAGICK_1_3_x
[pgmagick] cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++ [enabled by default]
[pgmagick] ./src/_ChannelType.cpp: In function 'void __ChannelType()':
[pgmagick] ./src/_ChannelType.cpp:24:31: error: 'GrayChannel' is not a member of 'Magick'
[pgmagick] ./src/_ChannelType.cpp:24:31: note: suggested alternative:
[pgmagick] /usr/include/ImageMagick/magick/magick-type.h:140:3: note:   'MagickCore::GrayChannel'
[pgmagick] error: command 'gcc' failed with exit status 1

Comments (4)

  1. Ondřej Čertík reporter

    I see what the problem is --- it is picking up imagemagick from Ubuntu, instead of graphicsmagick that I compiled myself...

    I can see that the include paths are hardwired in Is there any way to tell it my own path of graphicsmagick without patching

  2. Hideo Hattori repo owner

    How is it that uses an environment variable? (now, not implement)

    for example:

    MAGICK_INCLUDEPATH=/path/to/include easy_install pgmagick
  3. Log in to comment