You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This was originally reported via email from Luke Roskop from the GAMESS team.
Using GA --with-dmapp.
I am looking at different armci network setups that employ ComEx. On Titan (Cray Gemini network), I run into the following link error.
armci.c:(.text+0xfba): undefined reference to `comex_nbacc'
Looking at the following libraries:
nm --demangle libarmci.a |grep -ir comex_nbacc
U comex_nbacc
U comex_nbaccs
U comex_nbaccv
0000000000002092 T comex_nbaccs
00000000000025b3 T comex_nbaccv
nm --demangle libcomex.a |grep -ir comex_nbacc
0000000000002092 T comex_nbaccs
00000000000025b3 T comex_nbaccv
In my GA build, it does not appear that `comex_nbacc’ is defined.
Any Ideas?
The text was updated successfully, but these errors were encountered:
ARMCI_NbAcc used to be a #define to ARMCI_NbAccS back in the day and I suspect that is the issue here. You just have to add comex_nbacc that calls comex_nbaccs or something like that.
We fixed this same issue in other comex implementations, like #44. Clearly we don't use test or use our dmapp one. Cray provides a cray-ga module. I advised this user to avoid our dmapp implementation.
@jeffdaily It depends on the workload but I recall that the NWChem team uses MPI-PR instead of a DMAPP/uGNI version of ARMCI/ComEx on Cray machines. The DMAPP/uGNI ports have never worked reliably for me. Normally, I'd say that ARMCI-MPI is reliable, but it is currently blocked by a Cray MPI bug 🙁
This was originally reported via email from Luke Roskop from the GAMESS team.
Using GA --with-dmapp.
I am looking at different armci network setups that employ ComEx. On Titan (Cray Gemini network), I run into the following link error.
Looking at the following libraries:
In my GA build, it does not appear that `comex_nbacc’ is defined.
Any Ideas?
The text was updated successfully, but these errors were encountered: