Michael,

i will followup on that in the devel mailing list.


imho, there are three ways to see this :

1) this is an environment (e.g. user) issue: if you want it to work, then slurm should be rebuilt with pgi compiler.

2) this is a libtool issue : it does not support mixing .la files built with gcc and pgcc (e.g. -pthread option is unknown by pgcc)

3) this is an other libtool issue : -noswitcherror should be passed by libtool to the PGI compiler


Open MPI is not to be blamed here.

that being said, i am pragmatic so i do not mind hacking (one more time ...) libtool in OpenMPI to fix libtool or even make it PGI/GNU friendly


Cheers,


Gilles


On 7/26/2016 2:52 AM, Michael Di Domenico wrote:
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
_______________________________________________
users mailing list
us...@open-mpi.org
Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/users
Link to this post: 
http://www.open-mpi.org/community/lists/users/2016/07/29707.php


Reply via email to