mkoctfile does not understand "-fopenmp" from ImageMagick

[Søren Hauberg]

søn, 04 01 2009 kl. 21:37 -0700, skrev Alex Lancaster:
> OK, so the bug then is then really in the "image" octave-forge package
> (currently we are packaging version 1.0.2 as part of the current
> "bundle") , since it is the octave-forge package that actually does
> the calling of Magick++-config mkoctfile as part of the build step for
> that package.  It isn't something that's being done directly by the
> Fedora .spec file.
> 
> Where should such a bug be reported?  Is this the correct location?
> 
> https://lists.sourceforge.net/lists/listinfo/octave-dev
> 
> and if so, could you possibly forward the bug, as I'm not currently
> subscribed.  

Yes, that is the correct list. It's a semi-open list (i.e. with a
moderator) so you can send mails there even if you're not subscribed.

Anyway, I'm not planning on fixing this bug. Yeah, I know that is a
terrible thing to say, but let me explain...

'imread' and 'imwrite' are the functions in the image package that uses
ImageMagick. These have been rewritten and moved to the development
version of Octave. So Octave 3.2 will have these functions. Currently,
we are not planning on having a release of Octave-Forge until Octave 3.2
is released (seemed like a good decision at the time). So, the 'imread'
and 'imwrite' functions are no longer in Octave-Forge SVN, which makes
it more tedious to fix this issue.

Hmm, perhaps the no-octave-forge-release-until-3.2-is-out idea needs to
be re-discussed.

As to your problem, I'd recommend just changing the Makefile in the
image package to accommodate your needs. I know that is more work for
you, and I'm sorry, but I think it's the best I can do for you at the
moment :-(

Søren