Created attachment 206162 [details]
result of running "cd /usr/ports/graphics/openmp && make"
- FreeBSD 12.0 amd64
- rebuilding hugin after latest version bump (due to gcc8 -> gcc9 switch)
- The build fails right at the beginning with "c++: error: unsupported argument 'libomp -I/usr/local/include -L/usr/local/lib' to option 'fopenmp='"
- logfile attached
It seems that the c compiler should understand an option "-fopenmp=..." but cannot grok the inclusion of -I... and -L... in said option.
I could restart and successfully run to completion the build after the initial failure by editing the file work/.build/build.ninja, removing the double quotes from all lines containing the pattern
(in vi, using
But this is a manual solution.
Somehow the ninja file generated (by CMake?) includes the openmp C flags using double quotes when it should not, but I could not (yet) find out where this happens.
Is this still an issue? It seems that revision 507372 addresses the problem:
Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
Since then we have also released a new version of Hugin, and I haven't heard of any further issues.
This seems to be fixed, the recent build of hugin-2019.2.0_1 went through without glitches.