LEAP generally uses file system pipes and shared memory for interprocess communications. However, these forms of communication do not work on some network file systems, including AFS. Running on afs gives the following error:

Failed trying to open /afs/csail.mit.edu/u/t/tushar/LEAP/workspaces/test/build/default/hello_hybrid_exe/bm/null/pipes/platform_TO
output pipe WriterThread: No such file or directory"

LEAP provides an environmental variable LEAP_EXECUTION_DIRECTORY which can override LEAP default file paths so that the user can avoid file systems with insufficient support. Setting this variable to a local (or more full-featured) file system will solve the issue.