Charm++ parallel programming system

["Groner, Robert" <rug262 AT psu.edu>]

Sam,

Great, thanks for the help.  I did the build command you suggested with LIBS and the tests then built.  

The build help seemed to indicate that if I use the LIBS target, then it would build the additional libraries along with the charm++ core.  Do I understand that correct, or will I have to execute a build statement for the LIBS and then another one for charm++?

Thanks,

Rob Groner

Software Engineer

Institute for CyberScience

The Pennsylvania State University

222E Computer Building

University Park, PA 16802

Phone: 814.867.6074

---

From: White, Samuel T <white67 AT illinois.edu>
Sent: Thursday, August 10, 2017 4:35 PM
To: Groner, Robert; charm AT lists.cs.illinois.edu
Subject: RE: Problem building tests in charm++ 6.7.1

 

Hi Rob,

The EveryLB module is only built when you specify the "LIBS" target to the build script rather than the "charm++" target (./build LIBS mpi-linux-x86_64). We can fix our make test to not rely on EveryLB being built by default.

Thanks,
Sam White

---

From: Groner, Robert [rug262 AT psu.edu]
Sent: Thursday, August 10, 2017 3:17 PM
To: charm AT lists.cs.illinois.edu
Subject: [charm] Problem building tests in charm++ 6.7.1

I extracted the 6.7.1 archive, executed this build statement:

./build charm++ mpi-linux-x86_64 mpicxx smp --with-production --build-shared --basedir=$MPI_ROOT

That appeared to build without issue.

I then changed to the examples directory and executed "make".  That appeared to build without issue.

I then changed to the tests directory and executed "make".  It failed at this point:

../../../../bin/charmc -optimize -production  -language charm++ -o lb_test lb_test.o Topo.o -module CommonLBs

../../../../bin/charmc -optimize -production  -language charm++ -o lb_test.every lb_test.o Topo.o -module EveryLB

/opt/rh/devtoolset-4/root/usr/libexec/gcc/x86_64-redhat-linux/5.3.1/ld: cannot find -lmoduleEveryLB

collect2: error: ld returned 1 exit status

Fatal Error by charmc in directory /storage/home/rug262/development/charmxx/charm-6.7.1/tests/charm++/load_balancing/lb_test

   Command mpicxx -m64 -fPIC -D_REENTRANT -rdynamic -O2 -L/opt/aci/sw/openmpi/1.10.1_gcc-5.3.1/lib -fpic -O2 -L/opt/aci/sw/openmpi/1.10.1_gcc-5.3.1/lib -o lb_test.every -L../../../../bin/../lib -I../../../../bin/../include lb_test.o Topo.o moduleinit23929.o -lmoduleEveryLB -lckmain -lck -lmemory-default -lthreads-default -lconv-cplus-y -lconv-core -lconv-util -lconv-partition -lmemory-default -lthreads-default -lldb-rand -lconv-ldb -lpthread -lckqt -ldl -lmoduleEveryLB -lm returned error code 1

I went back to the output of the build command, and found this for EveryLB:

../bin/charmc -intrinsic -optimize -production  -build-shared EveryLB.ci && touch EveryLB.ci.stamp

After softlinking the headers, there was a section where dynamic libs were being built:

Performing '/usr/bin/gmake charm++ OPTS=-optimize -production QUIET=' in mpi-linux-x86_64-smp-mpicxx/tmp

../bin/charmc  -optimize -production  -build-shared -I.   -c -o DummyLB.o DummyLB.C

../bin/charmc  -optimize -production  -build-shared -o ../lib/libmoduleDummyLB.a DummyLB.o 

Warning: creating ../lib_so/libmoduleDummyLB.so 

ar: creating ../lib/libmoduleDummyLB.a

../bin/charmc  -optimize -production  -build-shared -I.   -c -o GreedyLB.o GreedyLB.C

../bin/charmc  -optimize -production  -build-shared -o ../lib/libmoduleGreedyLB.a GreedyLB.o 

Warning: creating ../lib_so/libmoduleGreedyLB.so ​

but EveryLB does not appear in this output.

Is there some additional parameter I need to add to "make" to make the tests build correctly?

Also, am I building the examples and tests correctly?  i could not find any parameter to add to the build statement to make it build examples and tests along with everything else.

Thanks.

Rob Groner

Software Engineer

Institute for CyberScience

The Pennsylvania State University

222E Computer Building

University Park, PA 16802

Phone: 814.867.6074