Opened 12 years ago

Last modified 7 years ago

#32642 closed defect

ImageMagick's PC files contain -fopenmp which makes GCC 4.0 fail — at Initial Version

Reported by: ballapete (Peter "Pete" Dyballa) Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.0.3
Keywords: openmp Cc: ryandesign@…, openmaintainer@…, nox@…
Port: ImageMagick

Description

When I try to compile GNU Emacs 24.0.92 with GCC 4.0 on Mac OS X 10.6.8 the configure script stops prematurely with:

checking for libXaw... configure: error: Lucid toolkit requires X11/Xaw include files

which config.log explains:

cc1: error: unrecognized command line option "-fopenmp"

This too modern switch is introduce from any of these PC files:

/opt/local/lib/pkgconfig/ImageMagick.pc:Cflags: -I${includedir} -fopenmp
/opt/local/lib/pkgconfig/MagickCore.pc:Cflags: -I${includedir} -fopenmp
/opt/local/lib/pkgconfig/MagickWand.pc:Cflags: -I${includedir} -fopenmp
/opt/local/lib/pkgconfig/Wand.pc:Cflags: -I${includedir} -fopenmp

One of them is asked by configure:

config.log:configure:10891: result: -fopenmp -I/opt/local/include/ImageMagick  

and than this compiler option is used. This is similar to tickets https://trac.macports.org/ticket/15945 and https://trac.macports.org/ticket/24944.

What about setting up a directory of backward compatible PC files without this -fopenmp switch?

My work-around is to copy a modified version of /opt/local/lib/pkgconfig/ImageMagick.pc into the root directory and modify PKG_CONFIG_PATH to contain .´´.

Change History (0)

Note: See TracTickets for help on using tickets.