llvm-config does not like being symlinked

[llvmbot]

Bugzilla Link	9136
Resolution	WORKSFORME
Resolved on	May 19, 2019 08:39
Version	trunk
OS	MacOS X
Reporter	LLVM Bugzilla Contributor
CC	@jryans

Extended Description

Currently I have a setup where my installation directory is not on the path for all users, so I create the installation in /contrib/projects/llvm and then symlink /contrib/projects/llvm/bin/llvm-config to /contrib/bin/llvm-config. This puts llvm-config on the users path, but if one runs 'llvm-config --lib-dir', one gets /contrib/lib instead of /contrib/projects/llvm/lib. This prevents any symlinking of llvm-config from being useful.

[llvmbot]

llvm-config: don't use the executable path if not in a development tree
I created a patch that should fix this issue. With this patch LLVM will use the prefix it was installed to instead of trying to guess the path based on where it was called from.

[llvmbot]

*** Bug llvm/llvm-bugzilla-archive#14700 has been marked as a duplicate of this bug. ***

[jryans]

This issue no longer seems to apply. Perhaps it was fixed via the move to CMake. In any case, symlinking llvm-config no longer changes the libdir result.