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
Right now we have the user run lstopo | grep -i coproc, which is an OK test, but it is possible A) for the right binary to be in your PATH but the wrong library to be found by ld B) the wrong binary to be in your PATH but the right library be found by ld. The latter is the case on Lassen where the module file only updated the LD_LIBRARY_PATH. We should just test the intended behavior directly with something like flux start flux resource list.
The text was updated successfully, but these errors were encountered:
Problem: Right now the documentation instructs the user to run `lstopo |
grep -i coproc`, which is an OK test, but it is possible:
1. for the right binary to be in the user's PATH but the wrong library
to be found by ld
2. the wrong binary to be in the user's PATH but the right library be
found by ld.
The latter is the case on Lassen where the module file only updates the
LD_LIBRARY_PATH.
Solution: Have the user test the intended behavior directly with
`flux start flux resource list`.
Closesflux-framework#71
Right now we have the user run
lstopo | grep -i coproc
, which is an OK test, but it is possible A) for the right binary to be in your PATH but the wrong library to be found byld
B) the wrong binary to be in your PATH but the right library be found byld
. The latter is the case on Lassen where the module file only updated the LD_LIBRARY_PATH. We should just test the intended behavior directly with something likeflux start flux resource list
.The text was updated successfully, but these errors were encountered: