#32642: ImageMagick's PC files contain -fopenmp which makes GCC 4.0 fail --------------------------------------+------------------------------------- Reporter: Peter_Dyballa@… | Owner: ryandesign@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: openmp | Port: ImageMagick --------------------------------------+------------------------------------- Changes (by ryandesign@…): * keywords: -fopenmp GCC 4.0 ImageMagick => openmp * cc: ryandesign@…, openmaintainer@…, nox@… (removed) * owner: macports-tickets@… => ryandesign@… Old 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 ``.´´.
New 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 #15945 and #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 ``.´´. -- Comment: That seems fraught... Wouldn't implementing #15945/#24944 (providing an openmp variant you could deselect) be the best solution? -- Ticket URL: <https://trac.macports.org/ticket/32642#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS