The fftw ebuild currently checks if gcc was compiled with the openmp use-flag when itself is emerged with the openmp flag. gcc-apple doesn't have such a flag and instead comes with openmp by default. So the ebuild should check if the current compiler is gcc-apple, or else one would have to install gcc just for (already existing) openmp support.
Created attachment 189264 [details, diff] Simple patch for the ebuild I wasn't sure what the right way is to check if the current compiler is gcc-apple. The patch just checks if "apple" is included in tc-getCC
(In reply to comment #1) > Created an attachment (id=189264) [edit] > Simple patch for the ebuild > > I wasn't sure what the right way is to check if the current compiler is > gcc-apple. The patch just checks if "apple" is included in tc-getCC > grobian: would this be better? Index: fftw-3.2.1.ebuild =================================================================== --- fftw-3.2.1.ebuild (revision 44166) +++ fftw-3.2.1.ebuild (working copy) @@ -22,7 +22,7 @@ FFTW_THREADS="--enable-threads --disable-openmp" fi if use openmp && - [[ $(tc-getCC)$ == *gcc* ]] && + [[ $(tc-getCC)$ != *apple* ]] && ( [[ $(gcc-major-version)$(gcc-minor-version) -lt 42 ]] || ! built_with_use sys-devel/gcc openmp ) then
I'd say not, since the built_with_use check uses sys-devel/gcc. (think of other compilers used like icc, sunstudio, open64, etc.) Hence, I'd do something like this: Index: fftw-3.2.1.ebuild =================================================================== --- fftw-3.2.1.ebuild (revision 44166) +++ fftw-3.2.1.ebuild (working copy) @@ -23,6 +23,6 @@ fi if use openmp && [[ $(tc-getCC)$ == *gcc* ]] && + [[ $(tc-getCC)$ != *apple* ]] && ( [[ $(gcc-major-version)$(gcc-minor-version) -lt 42 ]] || ! built_with_use sys-devel/gcc openmp ) then
Original patch applied, as it is what I suggested myself. Thanks!
