On Mon, Jul 25, 2016 at 4:53 AM, Gilles Gouaillardet <gil...@rist.or.jp> wrote: > > as a workaround, you can configure without -noswitcherror. > > after you ran configure, you have to manually patch the generated 'libtool' > file and add the line with pgcc*) and the next line like this : > > /* if pgcc is used, libtool does *not* pass -pthread to pgcc any more */ > > > # Convert "-framework foo" to "foo.ltframework" > # and "-pthread" to "-Wl,-pthread" if NAG compiler > if test -n "$inherited_linker_flags"; then > case "$CC" in > nagfor*) > tmp_inherited_linker_flags=`$ECHO "$inherited_linker_flags" | > $SED 's/-framework \([^ $]*\)/\1.ltframework/g' | $SED > 's/-pthread/-Wl,-pthread/g'`;; > pgcc*) > tmp_inherited_linker_flags=`$ECHO "$inherited_linker_flags" | > $SED 's/-framework \([^ $]*\)/\1.ltframework/g' | $SED 's/-pthread//g'`;; > *) > tmp_inherited_linker_flags=`$ECHO "$inherited_linker_flags" | > $SED 's/-framework \([^ $]*\)/\1.ltframework/g'`;; > esac > > > i guess the right way is to patch libtool so it passes -noswitcherror to $CC > and/or $LD, but i was not able to achieve that yet.
Thanks. I managed to work around the issue, by hand compiling the single module that failed during the build process. but something is definitely amiss in the openmpi compile system when it comes to pgi
