Hello,
Checked on #6a8fad4 and it looks fine.
$git show -1
commit 6a8fad49e57007cf8edce4ad8406f724d4e11f8f
Author: Ralph Castain <r...@open-mpi.org>
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 --with-pmi --enable-debug
Build examples:
$env PATH=$PWD/../install/bin:$PATH make
mpicc -g hello_c.c -o hello_c
mpicc -g ring_c.c -o ring_c
mpicc -g connectivity_c.c -o connectivity_c
make[1]: Entering directory
`/hpc/home/USERS/ivanovi/prj/ii-ompi-trunk/examples'
make[2]: Entering directory
`/hpc/home/USERS/ivanovi/prj/ii-ompi-trunk/examples'
mpifort -g hello_mpifh.f -o hello_mpifh
mpifort -g ring_mpifh.f -o ring_mpifh
make[2]: Leaving directory
`/hpc/home/USERS/ivanovi/prj/ii-ompi-trunk/examples'
make[1]: Leaving directory
`/hpc/home/USERS/ivanovi/prj/ii-ompi-trunk/examples'
make[1]: Entering directory
`/hpc/home/USERS/ivanovi/prj/ii-ompi-trunk/examples'
make[2]: Entering directory
`/hpc/home/USERS/ivanovi/prj/ii-ompi-trunk/examples'
shmemcc -g hello_oshmem_c.c -o hello_oshmem
make[2]: Leaving directory
`/hpc/home/USERS/ivanovi/prj/ii-ompi-trunk/examples'
make[2]: Entering directory
`/hpc/home/USERS/ivanovi/prj/ii-ompi-trunk/examples'
shmemcc -g ring_oshmem_c.c -o ring_oshmem
make[2]: Leaving directory
`/hpc/home/USERS/ivanovi/prj/ii-ompi-trunk/examples'
make[2]: Entering directory
`/hpc/home/USERS/ivanovi/prj/ii-ompi-trunk/examples'
Igor
On 14.09.2015 2:34, Jeff Squyres (jsquyres) wrote:
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 <phhargr...@lbl.gov> wrote:
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 changed if mpicc is being used today.
-Paul
On Sat, Sep 12, 2015 at 5:58 AM, Jeff Squyres (jsquyres) <jsquy...@cisco.com>
wrote:
On Sep 11, 2015, at 9:00 PM, Ralph Castain <r...@open-mpi.org> 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/bogus/lib
-loshmem -lmpi
The actual argv[0] of the executable should be determining which data file is
used to populate the underlying argv.
Probably best to open a github issue on this and assign to the OSHMEM devs to
figure out what is going on here...?
On Sep 11, 2015, at 5:43 PM, Ralph Castain <r...@open-mpi.org> 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 Squyres (jsquyres) <jsquy...@cisco.com> wrote:
Shouldn't you be using shmemcc, not mpicc?
On Sep 11, 2015, at 7:01 PM, Ralph Castain <r...@open-mpi.org> wrote:
On current master:
03:57:56 (topic/pmix) /home/common/openmpi/foobar/examples$ make ring_oshmem_c
mpicc -g ring_oshmem_c.c -o ring_oshmem_c
/tmp/ccfqcVje.o: In function `main':
/home/common/openmpi/foobar/examples/ring_oshmem_c.c:20: undefined reference to
`start_pes'
/home/common/openmpi/foobar/examples/ring_oshmem_c.c:21: undefined reference to
`_my_pe'
/home/common/openmpi/foobar/examples/ring_oshmem_c.c:22: undefined reference to
`_num_pes'
/home/common/openmpi/foobar/examples/ring_oshmem_c.c:32: undefined reference to
`shmem_int_put'
/home/common/openmpi/foobar/examples/ring_oshmem_c.c:44: undefined reference to
`shmem_int_wait_until'
/home/common/openmpi/foobar/examples/ring_oshmem_c.c:49: undefined reference to
`shmem_int_put'
collect2: error: ld returned 1 exit status
make: *** [ring_oshmem_c] Error 1
03:58:51 (topic/pmix) /home/common/openmpi/foobar/examples$ mpicc --showme
gcc -I/home/common/openmpi/build/foobar/include/openmpi
-I/home/common/openmpi/build/foobar/include/openmpi/opal/mca/hwloc/hwloc1110/hwloc/include
-I/home/common/openmpi/build/foobar/include/openmpi/opal/mca/event/libevent2022/libevent
-I/home/common/openmpi/build/foobar/include/openmpi/opal/mca/event/libevent2022/libevent/include
-I/home/common/openmpi/build/foobar/include -pthread -Wl,-rpath
-Wl,/home/common/openmpi/build/foobar/lib -Wl,--enable-new-dtags
-L/home/common/openmpi/build/foobar/lib -lmpi
03:59:12 (topic/pmix) /home/common/openmpi/foobar/examples$
None of the oshmem examples can be built - all fail with the same error. My
configure:
enable_orterun_prefix_by_default=yes
enable_mpi_thread_multiple=no
enable_mem_debug=no
enable_mem_profile=no
enable_debug_symbols=yes
enable_binaries=yes
enable_heterogeneous=no
enable_picky=yes
enable_debug=yes
enable_shared=yes
enable_static=no
enable_memchecker=no
enable_ipv6=no
enable_mpi_fortran=yes
enable_mpi_cxx=no
enable_mpi_cxx_seek=no
enable_cxx_exceptions=no
enable_mpi_java=no
enable_io_romio=no
enable_contrib_no_build=libnbc
with_memory_manager=no
with_tm=no
with_devel_headers=yes
with_portals=no
with_valgrind=no
if [ -n "$SLURMHOME" ] ; then
with_slurm=$SLURMHOME
with_pmi=$SLURMHOME
else
with_slurm=no
fi
Ralph
_______________________________________________
devel mailing list
de...@open-mpi.org
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
Link to this post:
http://www.open-mpi.org/community/lists/devel/2015/09/18010.php
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
_______________________________________________
devel mailing list
de...@open-mpi.org
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
Link to this post:
http://www.open-mpi.org/community/lists/devel/2015/09/18011.php
_______________________________________________
devel mailing list
de...@open-mpi.org
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
Link to this post:
http://www.open-mpi.org/community/lists/devel/2015/09/18014.php
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
_______________________________________________
devel mailing list
de...@open-mpi.org
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
Link to this post:
http://www.open-mpi.org/community/lists/devel/2015/09/18017.php
--
Paul H. Hargrove phhargr...@lbl.gov
Computer Languages & Systems Software (CLaSS) Group
Computer Science Department Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
_______________________________________________
devel mailing list
de...@open-mpi.org
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
Link to this post:
http://www.open-mpi.org/community/lists/devel/2015/09/18027.php
