esseks / monicelli

An esoteric programming language, come se fosse antani.
GNU General Public License v3.0
1.32k stars 52 forks source link

trouble compilation #31

Closed texrg closed 5 years ago

texrg commented 8 years ago

Hello, I use ubuntu and have trouble:

$ cmake ..
== Only a limited set of platforms was tested. We need your help!
== Report build errors to https://github.com/esseks/monicelli/issues
-- Boost version: 1.54.0
-- Found the following Boost libraries:
--   regex
--   system
--   filesystem
--   program_options
CMake Error at /usr/share/llvm-3.5/cmake/LLVMConfig.cmake:50 (include):
  include could not find load file:

    /usr/lib/llvm-3.5/share/llvm/cmake/LLVMExports.cmake
Call Stack (most recent call first):
  src/CMakeLists.txt:34 (find_package)

CMake Error at /usr/share/llvm-3.5/cmake/LLVMConfig.cmake:53 (include):
  include could not find load file:

    /usr/lib/llvm-3.5/share/llvm/cmake/LLVM-Config.cmake
Call Stack (most recent call first):
  src/CMakeLists.txt:34 (find_package)

CMake Error at src/CMakeLists.txt:74 (llvm_map_components_to_libnames):
  Unknown CMake command "llvm_map_components_to_libnames".

-- Configuring incomplete, errors occurred!

I have llvm-3.5 and the file exists:

$ls -l /usr/share/llvm-3.5/cmake/LLVMConfig.cmake
-rw-r--r-- 1 root root 13472 lut 12  2015 /usr/share/llvm-3.5/cmake/LLVMConfig.cmake

what is wrong?

robertodormepoco commented 8 years ago

the missing file(s) are /usr/lib/llvm-3.5/share/llvm/cmake/LLVMExports.cmake and /usr/lib/llvm-3.5/share/llvm/cmake/LLVM-Config.cmake

not /usr/share/llvm-3.5/cmake/LLVMConfig.cmake

esseks commented 8 years ago

You appear to have hit the bug in the Ubuntu/Debian package, as documented in the README. Sorry for the incovenience, unfortunately there is nothing I can do.

Until they fix it, llvm-3.5-dev from the LLVM APT repo should work just fine. I'd be grateful if you could confirm.

esseks commented 5 years ago

The newest release uses a version of LLVM which shouldn't be affected by the bug. I'm closing this bug as obsolete, but feel free to reopen if it reoccurs.