Yes, the clang package creates the symlink to the versioned binaries like clang-3.4 or clang-3.6. But you are out of luck if you want to have /usr/bin/clang to link to clang-3.6. For each release there is just one default llvm/clang release which the symlinks point to.
If you want to use the non-default clang version, you have to use the full binary name e.g. clang-3.6 or clang++-3.6. So from what you say it sounds more like the intended behaviour than a bug, albeit the inteded behaviour sadly does not help your use case. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to llvm-toolchain-3.6 in Ubuntu. https://bugs.launchpad.net/bugs/1566240 Title: clang-3.6 package does not install symlink Status in llvm-defaults package in Ubuntu: New Status in llvm-toolchain-3.6 package in Ubuntu: New Bug description: (was suggested to create this question as a bug) I'm a little uncertain as to whether this is a bug, or intended behaviour of the package. (Using Ubuntu 14.04.4 LTS (Kubuntu)) When I installed clang-3.6, it appears to (for some reason) conflict with the clang package from llvm-defaults, and had to remove clang and clang-3.4 to get 3.6 installed. Afterwards, /usr/bin/clang and /usr/bin/clang++ no longer exist. Is this because the overarching 'clang' package handles the creation of these symlinks? Or is this a bug with clang-3.6? I can obviously create my own symlink, but we have many people on different machines, and I'm keen to upgrade to 3.6 as it appears to solve an actual bug I had with clang-3.4 that caused the compiler to crash. I'd prefer not to have to ask them to create the symlinks themselves. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-defaults/+bug/1566240/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
