The error message isn’t complete because the long lines have been truncated, so it’s difficult to tell.
I know that boost plays some naming tricks, and it’s possible that they include the name of the linker in there, so that you’re in trouble if you’re using a different linker than boost was built with.
One way to step around all of this completely would be to use a container. Presumably Docker is out of the question because you’re running on a cluster where you don’t have root, but Singularity doesn’t require root and it can run Docker as well. I would be happy to build either a Docker or Singularity image containing hscPipe 6.5.1. If this appeals to you, you could take the LSST stack image out for a test drive:
lsst_latest_weekly () {
date +'w_%Y_%U'
}
singularity run -e -H ~/docker:/home/lsst -B ~/LSST:/home/lsst/LSST docker://lsstsqre/centos:7-stack-lsst_distrib-$(lsst_latest_weekly)
This uses the latest LSST weekly Docker (sometimes that may not point to anything if there’s been some trouble building the weekly as there has a couple of times recently, but I think that’s been resolved), maps the local ~/docker directory into the container’s homedir (to keep the real homedir and container homedir separate, in case that’s useful to you) and maps your real ~/LSST directory (which contains all my git clones) into the container’s ~/LSST so it picks up changes you make with your editor. Unlike Docker, Singularity lets you see the external world as well, so your cluster filesystem mounted at /clusterfs (or whatever) exists even when you’re in the Singularity container.
