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
On Mon, Jul 25, 2016 at 4:53 AM, Gilles Gouaillardet 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
Michael,
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 */
#
So, the -noswitcherror is partially working. I added the switch into
my configure line LDFLAGS param. I can see the parameter being passed
to libtool, but for some reason libtool is refusing to passing it
along at compile.
if i sh -x the libtool command line, i can see it set in a few
As a workaround, you can also try adding -noswitcherror to PGCC flags.
On 07/11/2016 03:52 PM, Åke Sandgren wrote:
Looks like you are compiling with slurm support.
If so, you need to remove the "-pthread" from libslurm.la and libpmi.la
On 07/11/2016 02:54 PM, Michael Di Domenico wrote:
I'm
You can also simply copy slurm (omitting the .la) into an other directory,
remove the .la, and pass this directory to Open MPI
an other option is to compile slurm with PGI compilers, so your *.la should
work fine.
You might be luckier by rebuilding slurm with gnu compilers and
No, you have to manually edit those two .la files by hand after
installation. It's basically a libtool problem. It generates the .la
file with an option that PGI dsoesn't understand.
On 07/14/2016 04:06 PM, Michael Di Domenico wrote:
> On Mon, Jul 11, 2016 at 9:52 AM, Åke Sandgren
On Mon, Jul 11, 2016 at 9:52 AM, Åke Sandgren wrote:
> Looks like you are compiling with slurm support.
>
> If so, you need to remove the "-pthread" from libslurm.la and libpmi.la
i don't see a configure option in slurm to disable pthreads, so i'm
not sure this is
On Thu, Jul 14, 2016 at 9:47 AM, Michael Di Domenico
wrote:
> Have 1.10.3 unpacked, ran through the configure using the same command
> line options as 1.10.2
>
> but it fails even earlier in the make process at
>
> Entering openmpi-1.10.3/opal/asm
> CPPAS atomic-asm.lo
>
Have 1.10.3 unpacked, ran through the configure using the same command
line options as 1.10.2
but it fails even earlier in the make process at
Entering openmpi-1.10.3/opal/asm
CPPAS atomic-asm.lo
This licensed Software was made available from Nvidia Corportation
under a time-limited beta license
Looks like you are compiling with slurm support.
If so, you need to remove the "-pthread" from libslurm.la and libpmi.la
On 07/11/2016 02:54 PM, Michael Di Domenico wrote:
> I'm trying to get openmpi compiled using the PGI compiler.
>
> the configure goes through and the code starts to compile,
On Mon, Jul 11, 2016 at 9:11 AM, Gilles Gouaillardet
wrote:
> Can you try the latest 1.10.3 instead ?
i can but it'll take a few days to pull the software inside.
> btw, do you have a license for the pgCC C++ compiler ?
> fwiw, FreePGI on OSX has no C++ license
Can you try the latest 1.10.3 instead ?
btw, do you have a license for the pgCC C++ compiler ?
fwiw, FreePGI on OSX has no C++ license and PGI C and gnu g++ does not work
together out of the box, hopefully I will have a fix ready sometimes this
week
Cheers,
Gilles
On Monday, July 11, 2016,
I'm trying to get openmpi compiled using the PGI compiler.
the configure goes through and the code starts to compile, but then
gets hung up with
entering: openmpi-1.10.2/opal/mca/common/pmi
CC common_pmi.lo
CCLD libmca_common_pmi.la
pgcc-Error-Unknown switch: - pthread
14 matches
Mail list logo