Re: [OMPI users] Open MPI unable to find threading support for PGI or Sun Studio
On Tue, 29 Jul 2008, Jeff Squyres wrote: On Jul 29, 2008, at 6:52 AM, Mark Dixon wrote: FWIW: I compile with PGI 7.1.4 regularly on RHEL4U4 and don't see this problem. It would be interesting to see the config.log's from these builds to see the actual details of what went wrong. ... Compiler OS Result === 32-bit 7.1.6 CentOS 5.2 (32-bit) no threading 32-bit 7.1.4 CentOS 5.2 (32-bit) no threading **config.log attached** 32-bit 7.1.4 RHEL4u6 (64-bit) works! 32-bit 7.1.4 CentOS 5.1 (64-bit) no threading ... I'm afraid this one is out of my bailiwick -- I don't know. Looking through your config.log file, it does look like this lack of __builtin_expect is the killer. FWIW, here's my configure output when I run with pgcc v7.1.4: ... I suggest that you bring this issue up with PGI support; they're fairly responsive on their web forums. ... In case anyone's interested, the fix is to upgrade to at least PGI 7.2-2. It seems that there was a change to glibc between RHEL4 and RHEL5 (2.3 vs. 2.5) which requires __builtin_expect to be defined when using certain pthread library functions. This also appears to be a problem for the Sun Studio 12 compiler (bug id 6603861), but it would seem that Sun's not in a hurry to fix it. Thanks for your time, Mark -- - Mark Dixon Email: m.c.di...@leeds.ac.uk HPC/Grid Systems Support Tel (int): 35429 Information Systems Services Tel (ext): +44(0)113 343 5429 University of Leeds, LS2 9JT, UK -
Re: [OMPI users] Segmentation fault: Address not mapped
On Jul 30, 2008, at 8:31 AM, James Philbin wrote: OK, to answer my own question, I recompiled OpenMPI appending '--with-memory-manager=none' to configure and now things seem to run fine. I'm not sure how this might affect performance, but at least it's working now. If you're not using OpenFabrics networks or older Myrinet (GM) networks, it won't impact performance at all. The memory manager is *only* used to improve the bandwidth of large messages on these networks. Maybe this can be put in the FAQ? Yes, it probably should be... I'll add it to the doc tickets for v1.3. Thanks for the heads up. -- Jeff Squyres Cisco Systems
[OMPI users] Problems building openmpi 1.2.6 with Lahey Fortran
I am trying to build OpenMPI-1.2.6 with Lahey Fortran, and I am running into problems. The issue is buliding shared libraries with Lahey. Lahey can do it, but they don't use the construct -fPIC to specify it. They use --shared. If I don't include anything, then the build fails near the end when linking with a Fortran object with an error message like: /usr/bin/ld: testcode.o: relocation R_X86_64_32S against `a local symbol' can not be used when making a shared object; recompile with -fPIC If I add --shared to FCFLAGS, the configure process will not finish (configure line below). It crashes because when it tries to build a small test program, it will seg fault. # ./configure FCFLAGS=--shared CC=gcc CXX=g++ F77=lf95 FC=lf95 F90=lf95 --prefix=/opt/openmpi/1.2.6-lahey-8.00a --without-gridengine --enable-io-romio --with-io-romio-flags=--with-file-sys=nfs+ufs --with-openib=/opt/hjet/ofed/1.3.1 Relevant config.log output: configure:36725: checking if Fortran compiler works configure:36781: lf95 -o conftest --shared conftest.f >&5 Encountered 0 errors, 0 warnings in file conftest.f. configure:36784: $? = 0 configure:36790: ./conftest ./configure: line 36791: 29048 Segmentation fault ./conftest$ac_exeext configure:36793: $? = 139 configure: program exited with status 139 configure: failed program was: | program main | | end So my hack to fix this was to add --shared to the FCFLAGS in ompi/mpi/f90/Makefile and build the code. What is the correct way for the configure process to know that if the compiler is lf95, to use --shared when compiling objects? Thanks, Craig -- Craig Tierney (craig.tier...@noaa.gov)
Re: [OMPI users] Segmentation fault: Address not mapped
Hi, I'm just using TCP so this isn't a problem for me. Any ideas what could be causing this segfault? James
