Hello,
Checked on #6a8fad4 and it looks fine.
$git show -1
commit 6a8fad49e57007cf8edce4ad8406f724d4e11f8f
Author: Ralph Castain
List-Post: devel@lists.open-mpi.org
Date: Fri Sep 11 02:01:25 2015 -0700
Configure:
--disable-vt --enable-orterun-prefix-by-default --enable-oshmem
--with-slurm --w
I actually tested manually before I replied -- I did a "make" in the examples
dir, and it used shmemcc. So something went wonky in Ralph's build for some
reason...?
> On Sep 12, 2015, at 11:52 AM, Paul Hargrove wrote:
>
> Another FYI.
> In my Aug 26 build of master (openmpi-dev-2371-gea935df
Another FYI.
In my Aug 26 build of master (openmpi-dev-2371-gea935df.tar.bz2) running
"make" in the examples directory *did* use shmemcc:
make[2]: Entering directory
`/home/phargrov/OMPI/openmpi-master-linux-x86_64-ss12u2/BLD/examples'
shmemcc -g ring_oshmem_c.c -o ring_oshmem
So, something has c
On Sep 11, 2015, at 9:00 PM, Ralph Castain wrote:
>
> FWIW: shemcc is just a symlink to mpicc, and I don’t see any -loshmem in that
> —showme output
$ shmemcc --showme
gcc -I/home/jsquyres/bogus/include -pthread -Wl,-rpath
-Wl,/home/jsquyres/bogus/lib -Wl,--enable-new-dtags -L/home/jsquyres/bo
FWIW: shemcc is just a symlink to mpicc, and I don’t see any -loshmem in that
—showme output
> On Sep 11, 2015, at 5:43 PM, Ralph Castain wrote:
>
> I typed “make” - the Makefile determines what to call. I suspect it isn’t
> calling the right thing
>
>
>> On Sep 11, 2015, at 4:17 PM, Jeff
I typed “make” - the Makefile determines what to call. I suspect it isn’t
calling the right thing
> On Sep 11, 2015, at 4:17 PM, Jeff Squyres (jsquyres)
> wrote:
>
> Shouldn't you be using shmemcc, not mpicc?
>
>
>> On Sep 11, 2015, at 7:01 PM, Ralph Castain wrote:
>>
>> On current master
Shouldn't you be using shmemcc, not mpicc?
> On Sep 11, 2015, at 7:01 PM, Ralph Castain wrote:
>
> On current master:
>
> 03:57:56 (topic/pmix) /home/common/openmpi/foobar/examples$ make
> ring_oshmem_c
> mpicc -gring_oshmem_c.c -o ring_oshmem_c
> /tmp/ccfqcVje.o: In function `main':
>
