The symlinks for the boost tools aren't being created. Here's a little snippet of the diff between versions 0.2 and 0.3: - pushd "${ROOT}/usr/bin/" 1>/dev/null - local tool - for tool in ${_boost_tools} ; do - [[ -e "${tool}" ]] && die -q "\"/usr/bin/${tool}\" exists and isn't a symlink" - [[ -e "${tool}-${version}" ]] && \ - ( ln -s "${tool}-${version}" "${tool}" || die -q "Couldn't create symlink \"/usr/bin/${tool}\"" ) - done + for t in ${python} ; do + pushd "$(dirname ${ROOT}${t})/.." 1>/dev/null + local ts="$(basename $(dirname ${ROOT}${t}))/${t//*\/}" + ts="${ts//${suffix}}" + local tt=${t//*\/} + ln -s "${ts}" "${tt}" || die -q "Couldn't create symlink \"$(pwd)/${tt}\"" There is, of course, no variable called 'python'. Reproducible: Always Steps to Reproduce: emerge -1 =eselect-boost-0.3 eselect boost update
can you please add the following information: a) which versions of boost do you have installed, including the use flags b) the version you're trying to select
I only have one version installed: boost-1.37.0-r1 USE="doc elibc_glibc expat icu kernel_linux mpi python tools userland_GNU x86" (flags taken from /var/db/pkg/.../USE).
If it wasn't obvious, the library symlinks are being created alright, but not the links for the tools like 'bjam'.
oh, that is by intention :-) The problem with bjam is that it has the boost-build path hardcoded in it. So my intention was that people needing boost-build will have to explicitly select the bjam version they want to use.
The eselect script will remove the symlink for bjam every time the boost eselect is run.
I need to use boost-1.37.0-r1. Can you suggest a workaround so that I can use eselect to set this version of Boost. Thanks!
