The current WiredTiger source code build and Autotools configure generate testing binaries that can be executed with the in-place directory structure on the same machine where those binaries are built. However, if the same source (including build) directory is copied over onto a different machine, or to a different directory on the same machine, calling those testing binaries would run into problem failing to locate the required dynamic libraries, as the RPATH is set to a hard-code directory by the initial build. 

This issue became obvious after WiredTiger tests were migrated over to Evergreen. WT-5151 and WT-5685 are different reflections of the same underlying issue described above. 

In order to make testing binaries relocatable across machines and folders, one possibility is to enable a portable RPATH setting using $ORIGIN (instead of hardcoded value), ideally during the building phase.