mkoctfile does not understand "-fopenmp" from ImageMagick

Alex Lancaster alexl at users.sourceforge.net
Sun Jan 4 22:37:29 CST 2009


>>>>> "JWE" == John W Eaton  writes:

[...]

JWE> I don't think mkoctfile should be modified every time some new
JWE> linker flags appear.

JWE> If you need to pass flags specifically to the linker, then you
JWE> can use the -Wl,... option.  For example, use

JWE>   -Wl,-fopenmp

JWE> Since you are getting the flags from a config script, you'll need
JWE> to process them first to prepend each of the ldflags with "-Wl,",
JWE> then pass the result to mkoctfile.

Thanks for the clarification,

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.  

Thanks,

Alex


More information about the Bug-octave mailing list