llvm-config is not in the package

[Matt Giuca]

Binary package hint: llvm

I've just installed llvm-dev on a fresh Maverick system. It doesn't contain the 'llvm-config' program (which I know exists because I have it on another system, though I don't know which package it was in). llvm-dev is including llvm-dev-2.8 which includes llvm-2.8.

When I type llvm-config, it says:
The program 'llvm-config' is currently not installed. You can install it by typing:
sudo apt-get install llvm-2.7

That seems to be incorrect, since the latest version is 2.8. But okay, I separately install the package llvm-2.7. Also llvm-2.7-dev for good measure. But none of those packages contain llvm-config. I don't actually know which package llvm-config is in, if any. But there are at least two problems here:
- Typing 'llvm-config' should not tell me to install an old version of llvm, and
- llvm-config should be included in the llvm-2.8-dev package.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Jonas Finnemann Jensen (jopsen)]

I got llvm 3.0 installed, but it contains llvm-config-3.0, maybe there should be some update-alternatives magic, or something to decide which llvm-config version llvm-config should link to... I kind of think it's nice that we can have parallel installs of llvm, creating the link my self is no problem, just a bit ugly...

Anyways, just my two cents, lot of projects use llvm-config, so having some way of choosing which to use, as in llvm-config-3.0 or llvm-config-2.8, etc... Might solve this issue...

[Matthias Klose (doko)]

closing this as won't fix. llvm-config is now provided by llvm-dev.

llvm-config should NOT be handled with alternatives, because different llvm versions are ABI/API incompatible. packages really should accept an explicit llvm version number, or provide something like --with-llvm-config=llvm-config-3.x (as openjdk/icedtea does).