PoD submissions fail on lxbatch because it uploads the interactive user environment and in addition, inserts /use/lib64 in the LD_LIBRARY_PATH. As such, if a door / PoD version compiled with an external compiler is used (e.g. gcc 4.7 or 4.8), it will fail because the incorrect libstdc++ lib is picked up first in the path from /usr/lib64.
lsf allows to suppress uploading of user interactive environment to the batch job with a -L option. Can this be configured in .PoD/PoD.cfg (I don't see this in the documentation or cfg file) or another mechanism devised to overcome this ?
PoD submissions fail on lxbatch because it uploads the interactive user environment and in addition, inserts /use/lib64 in the LD_LIBRARY_PATH. As such, if a door / PoD version compiled with an external compiler is used (e.g. gcc 4.7 or 4.8), it will fail because the incorrect libstdc++ lib is picked up first in the path from /usr/lib64.
lsf allows to suppress uploading of user interactive environment to the batch job with a -L option. Can this be configured in .PoD/PoD.cfg (I don't see this in the documentation or cfg file) or another mechanism devised to overcome this ?
Thanks !
regards, Asoka