Re: [OMPI users] problem with MPI_Comm_spawn in 1.6.5 but not 1.4.3 or 1.8.4

2015-03-12 Thread Ralph Castain
Indeed sounds like a bug in 1.6.5, but we no longer maintain that series. I'm afraid an upgrade to the 1.8 series is the only solution. > On Mar 12, 2015, at 6:11 PM, Chris Paciorek > wrote: > > I'm having an issue with MPI_Comm_spawn not starting workers on the > nodes provided via -machinef

[OMPI users] problem with MPI_Comm_spawn in 1.6.5 but not 1.4.3 or 1.8.4

2015-03-12 Thread Chris Paciorek
I'm having an issue with MPI_Comm_spawn not starting workers on the nodes provided via -machinefile or -host. This is occurring on Ubuntu 14.04/14.10 with openMPI 1.6.5. However, I do not have the problem on Ubuntu 12.04 with openMPI 1.4.3 nor is there a problem when I install openMPI 1.8.4 from so

Re: [OMPI users] Cannot compile 1.8.x with intel 12.1 and 'io-romio' enabled

2015-03-12 Thread Fabricio Cannini
On 12-03-2015 20:44, Jeff Squyres (jsquyres) wrote: Gah; my mistake -- that va_end(fmt) should be va_end(list). It works for me with gcc 4.9.1 and icc: Intel(R) C Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 15.0.2.164 Build 20150121 Ah, ok. I've made the change,

Re: [OMPI users] Cannot compile 1.8.x with intel 12.1 and 'io-romio' enabled

2015-03-12 Thread Jeff Squyres (jsquyres)
Gah; my mistake -- that va_end(fmt) should be va_end(list). It works for me with gcc 4.9.1 and icc: Intel(R) C Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 15.0.2.164 Build 20150121 > On Mar 12, 2015, at 7:40 PM, Fabricio Cannini wrote: > > On 12-03-2015 20:24,

Re: [OMPI users] Cannot compile 1.8.x with intel 12.1 and 'io-romio' enabled

2015-03-12 Thread Fabricio Cannini
On 12-03-2015 20:24, Jeff Squyres (jsquyres) wrote: include #include static void foo(const char *fmt, ...) { va_list list; va_start(list, fmt); vprintf(fmt, list); va_end(fmt); } int main() { foo("%s %s\n", "hello", "world"); } Thanks for the cod

Re: [OMPI users] Cannot compile 1.8.x with intel 12.1 and 'io-romio' enabled

2015-03-12 Thread Jeff Squyres (jsquyres)
Put this in foo.c: - include #include static void foo(const char *fmt, ...) { va_list list; va_start(list, fmt); vprintf(fmt, list); va_end(fmt); } int main() { foo("%s %s\n", "hello", "world"); } - Then try icc foo.c -o foo ./foo > On Mar

Re: [OMPI users] Process Binding Warning

2015-03-12 Thread Ralph Castain
You are missing the numactl and numactl-devel packages on that compute node, and so we cannot bind the memory to the same location as your proc. As the warning indicates, it can impact performance but won't stop you from running > On Mar 12, 2015, at 12:51 PM, Saliya Ekanayake wrote: > > Hi,

Re: [OMPI users] Cannot compile 1.8.x with intel 12.1 and 'io-romio' enabled

2015-03-12 Thread Fabricio Cannini
On 12-03-2015 18:23, Jeff Squyres (jsquyres) wrote: Do you have the latest version of the Intel 12.x compiler installed? Are you able to compile/install any other C source code that uses varargs? I'll try it now. Any easy-to-find code tha i can pick? Sorry but I know practically zero C. :(

Re: [OMPI users] Cannot compile 1.8.x with intel 12.1 and 'io-romio' enabled

2015-03-12 Thread Jeff Squyres (jsquyres)
Do you have the latest version of the Intel 12.x compiler installed? Are you able to compile/install any other C source code that uses varargs? I ask because we've seen busted / buggy Intel compiler installs before. It may be that you need to update to the latest version of the Intel 12.x compi

[OMPI users] Cannot compile 1.8.x with intel 12.1 and 'io-romio' enabled

2015-03-12 Thread Fabricio Cannini
Hello there I'm trying to compile the mentioned combination in a centos 6.5 x64 host without success, while using intel 14.0 the problem does not happens. Using the configure option '--disable-io-romio' allows me to compile without further trouble, but that's not really a fix. ;) I've tried

[OMPI users] Process Binding Warning

2015-03-12 Thread Saliya Ekanayake
Hi, I am getting the following binding warning and wonder if I am missing some library or so -- WARNING: a request was made to bind a process. While the system supports binding the process itself, at least one node does NOT s