gcc 3.3 cmath undefined errors

[Wesley Smith]

I have the most recent stable release of Imagemagick.  I managed to
get it to compile finally with some help from one of the authors.  I
unsitalled Imagemagick and installed Graphicsmagick (basically the
same thing).  Instead of using xcode which does some ridiculous things
with compiler options and wouldn't let me do what I need to do, I
compiled from the terminal with:

c++ -o main main.cpp `GraphicsMagick++-config --cppflags --cxxflags
--ldflags --libs`

the last part is a script installed with Graphicsmagick that sets the
proper flags settings from easy compilation.  This worked.  I stil
haven't figured out a way to get Xcode to do this, and I think I'm
going to give up and just do a makefile.  Fie on thee Apple!  Now to
get it to work with FLTK.

wes

On 5/20/05, Nix <nix@esperi.org.uk> wrote:
> On 19 May 2005, Wesley Smith prattled cheerily:
> > Apparently, on OSX, gcc dynamically calls g++ or gcc depending on the
> > source file extension names.  In any case, I tried calling g++ from
> > the command line and got the same errors.  I'm using a library called
> > Imagemagick (thus the magick++).  Here's my code:
> >
> > #include <Magick++.h>
> > #include <iostream>
> >
> > using namespace std;
> >
> > int main(int argc, char **argv)
> > {
> >       Magick::Image image;
> >       image.read("/Users/na/Documents/IGERT/vcsel.gif" );
> >
> >       return 0;
> > }
> 
> This works flawlessly with ImageMagick-6.2.1 on Linux.
> 
> What version of ImageMagick do you have? Some (distinctly aged) versions
> of Magick++ had problems with namespace std :(
> 
> --
> `End users are just test loads for verifying that the system works, kind of
>  like resistors in an electrical circuit.' - Kaz Kylheku in c.o.l.d.s
>