[Bug 255894] devel/llvm-devel: create a static libs flavor
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sat May 15 05:23:17 UTC 2021
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255894
Bug ID: 255894
Summary: devel/llvm-devel: create a static libs flavor
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: brooks at FreeBSD.org
Reporter: dereks at lifeofadishwasher.com
Assignee: brooks at FreeBSD.org
Flags: maintainer-feedback?(brooks at FreeBSD.org)
When trying to build include-what-you-use master branch (combined with llvm's
main ex: llvm-devel) llvm cmake files attempt to use static libs which fails
since static libs option is disabled (rm'ed post install).
...CMake Error at /usr/local/llvm-devel/lib/cmake/llvm/LLVMExports.cmake:1413
(message):
The imported target "LLVMDemangle" references the file
"/usr/local/llvm-devel/lib/libLLVMDemangle.a"
but this file does not exist. Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
"/usr/local/llvm-devel/lib/cmake/llvm/LLVMExports.cmake"
but not all the files it references.
Call Stack (most recent call first):
/usr/local/llvm-devel/lib/cmake/llvm/LLVMConfig.cmake:285 (include)
CMakeLists.txt:19 (find_package)
...
It appears llvm-devel doesn't have a build option to not build static libs so
the ports option is just deleting the files. So I believe that's the case:
* The installation package was faulty and contained
Should the static libs not be an option? Or should additional modifications be
applied to the cmake files?
Is it possible to have a new flavor that would create a package that only
contains the static libs being deleted?
Assuming this option will be a part of devel/llvm13 when the time comes it
would break devel/include-what-you-use since the option is disabled.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list