> - I am using boost 1.37 or boost 1.35 or boost - I don't know if
> that's good, but at least it gives more testing control over various
> boost libraries:
> libboost1.37-dev | libboost1.35-dev | libboost-dev,
> libboost-filesystem1.37-dev | libboost-filesystem1.35-dev |
> libboost-filesystem-dev,
> libboost-regex1.37-dev | libboost-regex1.35-dev | libboost-regex-dev,
> libboost-iostreams1.37-dev | libboost-iostreams1.35-dev |
> libboost-iostreams-dev,
> libboost-test1.37-dev | libboost-test1.35-dev | libboost-test-dev,
Whilst this works great in a pbuilder, it doesn't work in Debian - build dependencies with a | in are ignored by the Debian build infrastructure, and only the first entry is used. If you want to use the distro's default boost version, I'd recommend only the libboost-dev et al build-deps.
> - I am using boost 1.37 or boost 1.35 or boost - I don't know if filesystem1. 37-dev | libboost- filesystem1. 35-dev | filesystem- dev, regex1. 37-dev | libboost- regex1. 35-dev | libboost-regex-dev, iostreams1. 37-dev | libboost- iostreams1. 35-dev | iostreams- dev, test1.37- dev | libboost- test1.35- dev | libboost-test-dev,
> that's good, but at least it gives more testing control over various
> boost libraries:
> libboost1.37-dev | libboost1.35-dev | libboost-dev,
> libboost-
> libboost-
> libboost-
> libboost-
> libboost-
> libboost-
Whilst this works great in a pbuilder, it doesn't work in Debian - build dependencies with a | in are ignored by the Debian build infrastructure, and only the first entry is used. If you want to use the distro's default boost version, I'd recommend only the libboost-dev et al build-deps.