Re: [OMPI users] building openmpi-v1.8.5-46-g9f5f498 still breaks

> On Jun 10, 2015, at 6:27 AM, Jeff Squyres (jsquyres) > wrote: > >> i just found an other issue with this scenario : >> symlinks in the profile directories (ompi/mpi/c/profile, >> ompi/mpi/fortran/mpif-h/profile, oshmem/shmem/c/profile) are not recreated >> and points to

Re: [OMPI users] building openmpi-v1.8.5-46-g9f5f498 still breaks

it is a bit different for those links since they are created only if they do not exist. I guess thede links should be recreated if they are older than Makefile btw, does make check for the date of the symlink or the linked file ? On Wednesday, June 10, 2015, Jeff Squyres (jsquyres)

Re: [OMPI users] building openmpi-v1.8.5-46-g9f5f498 still breaks

On Jun 10, 2015, at 12:00 AM, Gilles Gouaillardet wrote: > > that can happen indeed, in a complex but legitimate environment : > > mkdir ~/src > cd ~/src > tar xvfj openmpi-1.8.tar.bz2 > mkdir ~/build/openmpi-v1.8 > cd ~/build/openmpi-v1.8 > ~/src/openmpi-1.8/configure > make

Re: [OMPI users] building openmpi-v1.8.5-46-g9f5f498 still breaks

On Jun 10, 2015, at 1:35 AM, Siegmar Gross wrote: > >> I don't see any reason why this should be happening to you only >> sometimes; this code has been unchanged in *forever*. :-( > > It only happens since openmpi-v1.8.5-40-g7b9e672 which I tried to >

Re: [OMPI users] building openmpi-v1.8.5-46-g9f5f498 still breaks

Hi Gilles, > then i cannot figure out how this can happen ... > > i see you remove the install dir (/usr/local/...) > but i do not see you removing the build directory : > > i see > > mkdir openmpi-1.8.6-${SYSTEM_ENV}.${MACHINE_ENV}.64_gcc > cd openmpi-1.8.6-${SYSTEM_ENV}.${MACHINE_ENV}.64_gcc

Re: [OMPI users] building openmpi-v1.8.5-46-g9f5f498 still breaks

Siegmar, then i cannot figure out how this can happen ... i see you remove the install dir (/usr/local/...) but i do not see you removing the build directory : i see mkdir openmpi-1.8.6-${SYSTEM_ENV}.${MACHINE_ENV}.64_gcc cd openmpi-1.8.6-${SYSTEM_ENV}.${MACHINE_ENV}.64_gcc but i do not see

Re: [OMPI users] building openmpi-v1.8.5-46-g9f5f498 still breaks

Hi Gilles, > a simple workaround is you always run configure in an empty directory > in this example, please recreate > > rm -rf /export2/src/openmpi-1.8.6/openmpi-1.8.6-Linux.x86_64.64_gcc > mkdir /export2/src/openmpi-1.8.6/openmpi-1.8.6-Linux.x86_64.64_gcc > > before invoking configure and

Re: [OMPI users] building openmpi-v1.8.5-46-g9f5f498 still breaks

Hi Jeff, > I don't see any reason why this should be happening to you only > sometimes; this code has been unchanged in *forever*. :-( It only happens since openmpi-v1.8.5-40-g7b9e672 which I tried to build June 1th and on all versions following-up which I tried (openmpi-v1.8.5-43-g0dd996b,

Re: [OMPI users] building openmpi-v1.8.5-46-g9f5f498 still breaks

Siegmar -- I don't see any reason why this should be happening to you only sometimes; this code has been unchanged in *forever*. :-( Did your NFS server drift out of time sync with your build machine, perchance? Regardless, I just pushed what should be a workaround to master and I'll PR it

[OMPI users] building openmpi-v1.8.5-46-g9f5f498 still breaks

Hi, today I tried to build openmpi-v1.8.5-46-g9f5f498 on my machines (Solaris 10 Sparc, Solaris 10 x86_64, and openSUSE Linux 12.1 x86_64) with gcc-4.9.2 and Sun C 5.13 and I got the same error on all three platforms with both compilers. I have already reported the problem a few days ago. I used