[Llvm-bgq-discuss] pulling in mpi using clang

[Hal Finkel]

Geoffrey,

Use the wrapper scripts in:
/home/projects/llvm/mpi/clang/bin/
or
/home/projects/llvm/mpi/clang.legacy/bin/
depending on which version of MPI you'd like (legacy has a global MPI lock, and so it is for apps that only call MPI from one thread)

 -Hal

----- Original Message -----
> From: "Geoffrey Irving" <irving at naml.us>
> To: llvm-bgq-discuss at lists.alcf.anl.gov
> Sent: Friday, February 1, 2013 12:16:34 AM
> Subject: [Llvm-bgq-discuss] pulling in mpi using clang
> 
> What's the proper way to get mpi when using
> /home/projects/llvm/current/bin/bgclang++?  Previously, I stole the
> flags from the gcc mpi wrapper (I unfortunately do not remember how I
> did this), and then manually specifiied
> 
>     -I/bgsys/drivers/V1R1M2/ppc64/comm/sys/include
> -I/bgsys/drivers/V1R1M2/ppc64
> -I/bgsys/drivers/V1R1M2/ppc64/spi/include
> -I/bgsys/drivers/V1R1M2/ppc64/spi/include/kernel/cnk
> -I/bgsys/drivers/V1R1M2/ppc64/comm/gcc/include
>     -Wl,-rpath=/bgsys/drivers/V1R1M2/ppc64/comm/gcc/lib
> -Wl,-rpath=/bgsys/drivers/V1R1M2/ppc64/comm/sys/lib
> -Wl,-rpath=/bgsys/drivers/V1R1M2/ppc64/spi/lib
> -L/bgsys/drivers/V1R1M2/ppc64/comm/gcc/lib
> -L/bgsys/drivers/V1R1M2/ppc64/comm/sys/lib
> -L/bgsys/drivers/V1R1M2/ppc64/spi/lib -lmpich -lopa -lmpl -lrt -ldl
> -lpami -lSPI -lSPI_cnk -lpthread
> 
> This seems fairly sketchy, so I'd like to do it the right way if such
> exists, especially if the driver versions are going to change soon.
> Are there wrapper compilers set up?
> 
> If I do the above manual way, and qsub a job, it errors out during
> launch with
> 
> 2013-01-31 17:21:50.888 (INFO ) [0xfff7f4ba210]
> 14558:ibm.runjob.AbstractOptions: using properties file
> /bgsys/local/etc/bg.properties
> 2013-01-31 17:21:50.889 (INFO ) [0xfff7f4ba210]
> 14558:ibm.runjob.AbstractOptions: max open file descriptors: 65536
> 2013-01-31 17:21:50.889 (INFO ) [0xfff7f4ba210]
> 14558:ibm.runjob.AbstractOptions: core file limit: 0
> 2013-01-31 17:21:50.889 (INFO ) [0xfff7f4ba210]
> 14558:tatu.runjob.client: scheduler job id is 54725
> 2013-01-31 17:21:50.891 (INFO ) [0xfffadf71a70]
> 14558:tatu.runjob.monitor: monitor started
> 2013-01-31 17:21:50.892 (INFO ) [0xfff7f4ba210]
> VST-20400-31511-32:14558:ibm.runjob.client.options.Parser: set local
> socket to runjob_mux from properties file
> 2013-01-31 17:21:51.319 (FATAL) [0xfff7f4ba210]
> VST-20400-31511-32:14558:ibm.runjob.client.Job: could not start job:
> job failed to start
> 2013-01-31 17:21:51.319 (FATAL) [0xfff7f4ba210]
> VST-20400-31511-32:14558:ibm.runjob.client.Job: Load failed on
> Q02-I4-J04: Application executable ELF header contains invalid value,
> errno 8 Exec format error
> 2013-01-31 17:21:51.320 (INFO ) [0xfff7f4ba210] tatu.runjob.client:
> task exited with status 1
> 2013-01-31 17:21:54.634 (INFO ) [0xfffadf71a70]
> 14558:tatu.runjob.monitor: tracklib completed
> 2013-01-31 17:21:54.634 (INFO ) [0xfffadf71a70]
> 14558:tatu.runjob.monitor: monitor terminating
> 2013-01-31 17:21:54.635 (INFO ) [0xfff7f4ba210] tatu.runjob.client:
> monitor completed
> 
> It's possible this is unrelated, of course.
> 
> Thanks,
> Geoffrey
> _______________________________________________
> llvm-bgq-discuss mailing list
> llvm-bgq-discuss at lists.alcf.anl.gov
> https://lists.alcf.anl.gov/mailman/listinfo/llvm-bgq-discuss
>