Re: [OMPI users] Build failure with OMPI-1.5 (clang-2.8, gcc-4.5.1 with debug options)

> On Thu, Oct 14, 2010 at 22:36, Jeff Squyres wrote: > > > On Oct 11, 2010, at 4:50 PM, Jed Brown wrote: > > > > > Note that this is an out-of-source build. > > > > > > $ ../configure --enable-debug --enable-mem-debug > > --prefix=/home/jed/usr/ompi-1.5-clang CC=clang

Re: [OMPI users] Build failure with OMPI-1.5 (clang-2.8, gcc-4.5.1 with debug options)

On Friday 15 October 2010 16:56:50 you wrote: > > On Thu, Oct 14, 2010 at 22:36, Jeff Squyres wrote: > > > On Oct 11, 2010, at 4:50 PM, Jed Brown wrote: > > > > Note that this is an out-of-source build. > > > > > > > > $ ../configure --enable-debug --enable-mem-debug > > > >

Re: [OMPI users] [SPAM:### 85%] Re: [SPAM:### 83%] problem when compiling ompenmpiV1.5.1

/otfprofile $ cat otfprofile.cpp | sed -e "s/_OPENMP/NEVER_DEFINED/" >tmp $ mv tmp otfprofile.cpp Matthias Jurenz > On Dec 16, 2010, at 6:49 AM, Jeff Squyres wrote: > > Hmm. I thought we had squashed all VT OMP issues. Bummer. > > Can you send all the information located he

Re: [OMPI users] VampirTrace integration with VT_GNU_NMFILE environment variable

Hello, first, please consider that the VT versions integrated in Open MPI v1.5.x and v1.4.x are different - respectively the names of the environment variables for setting a pre-created symbol list: Open MPI v1.4.x: VT_NMFILE Open MPI v1.5.x: VT_GNU_NMFILE Furthermore, make

Re: [OMPI users] problems compiling openmpi-1.6 on some platforms

Hello, the patch below fixes the build issue on Solaris 10. Please apply it to Open MPI 1.6 as follows: $ cd openmpi-1.6 $ patch -p1 From: Siegmar Gross > Subject: [OMPI users] problems compiling openmpi-1.6 on some platforms > Date: May 30, 2012 7:29:31

Re: [OMPI users] undefined reference to `__intel_sse2_strlen'

Hello Thomas, this error typically occurs when different compiler suites used for compiling C/C++ mixed source code. Please add CXX=icpc to your configure command in order to use a single compiler suite (=Intel) for compiling Open MPI. Otherwise, CXX is set to the default compiler (=g++) which

Re: [OMPI users] OpenMPI 1.7rc5 fails to build with CUDA support when CUDA is in a non-standard location

Hello Adam, thanks for the hint! The upcoming v1.7 release (or candidate) will include a fix for this problem. With regards, Matthias

Re: [OMPI users] OpenMPI 1.7rc5 fails to build with CUDA support when CUDA is in a non-standard location

Hello Adam, > I was able to build successfully by manually substituting the correct location into the Makefile in question. Another, more convenient workaround would be to add the following option to the Open MPI configure command: --with-contrib-vt-flags="--with-cuda-dir=$CUDA_HOME" The

Re: [OMPI users] problem building openmpi-1.9a1r27751 on Solaris 10

Hallo Siegmar, thanks for your report! The build issue should be fixed in revision 27770, so just give it a try. With regards, Matthias Jurenz > From: Siegmar Gross <siegmar.gr...@informatik.hs-fulda.de> > Subject: [OMPI users] problem building openmpi-1.9a1r27751 on Solaris 10 >

Re: [OMPI users] Error compiling openmpi-1.6.4a1r27766 on Solaris 10

/acinclude.execwrap.m4 ompi/contrib/vt/vt/vtlib/vt_execwrap.c Regards, Matthias Jurenz > Hi > I tried to build openmpi-1.6.4a1r27766 on Solaris 10 Sparc and x86_64 with Sun C 5.12 and gcc-4.7.1 and got the following error for all combinations. > ... CC vt_execwrap.lo "../../../../../../openmpi

Re: [OMPI users] OpenMPI 1.6 with Intel 11 Compiler

Did you verified that your icpc works properly? Can you compile other C++ applications with icpc? It might be that your version of icpc isn't supported with that version of gcc. I've found a ticket where a similar problem was reported: https://svn.open-mpi.org/trac/ompi/ticket/3077 The solution

Re: [OMPI users] 32-/64-bit library problem in openmpi-1.7rc8r28176 and openmpi-1.9r28175

Hi Siegmar, the problem is that FCFLAGS is not passed to the Fortran compiler. Fixed in revision 28228. Thanks for the hint! Kind regards, Matthias On Mar 21, 2013, at 9:29 AM, Siegmar Gross wrote: > Hi > > today I tried to build

Re: [OMPI users] questions about tracing OpenMPI program

Dear Lin, for a quick view of what is inside the trace you could try 'otfprofile' to generate a tex/ps file with some information. This tool is a component of the latest stand-alone version of the Open Trace Format (OTF) - see http://www.tu-dresden.de/zih/otf/. However, if you need more detailed

Re: [OMPI users] building the 1.4.1 rpm under RHEL 5

Hello Dave, unfortunately, we have no such platform for trying to reproduce this error, but we would be pleased, if you could help us to identify the problem. We guess that the following will fix the problem: Could you please insert the line #undef fprintf in the file

Re: [OMPI users] Question - OTF file

Hello Arthur, the files which you obtained look good to me and you did the correct approach to get these files. Did you get any error message from Vampir? Do the trace work with the OTF tools 'otfdump' or 'otfprofile'? Matthias On Thursday 25 March 2010 04:16:21 Arthur Trojanowski wrote: >