Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

problem in configure and make #96

Open
Git-zyj opened this issue Aug 3, 2023 · 3 comments
Open

problem in configure and make #96

Git-zyj opened this issue Aug 3, 2023 · 3 comments

Comments

@Git-zyj
Copy link

Git-zyj commented Aug 3, 2023

configure.ac line 107:

AC_CHECK_PROG(FILECHECK,FileCheck,yes,no,path = "$CLANG_PREFIX/bin:$PATH:/usr/lib64/llvm")

should be:

AC_CHECK_PROG(FILECHECK,FileCheck,yes,no,$CLANG_PREFIX/bin:$PATH:/usr/lib64/llvm)

otherwise "llvm FileCheck" cannot be found when configuring:

checking for FileCheck... no
configure: error: Please install LLVM FileCheck before configuring.

@Git-zyj Git-zyj changed the title bug in configure.ac problem in configure and make Aug 7, 2023
@Git-zyj
Copy link
Author

Git-zyj commented Aug 7, 2023

After I changed the configure.ac file as above, the configure process worked well.

However, there is another problem for make:

make[2]: Entering directory '/home/zyj/pluto/pet'
CXXLD pet_check_code
/usr/bin/ld: ./.libs/libpet.so: undefined reference to `clang::CompilerInvocation::setLangDefaults(clang::LangOptions&, clang::InputKind, llvm::Triple const&, std::vector<std::__cxx11::basic_string<char, std::char_traits, std::allocator >, std::allocator<std::__cxx11::basic_string<char, std::char_traits, std::allocator > > >&, clang::LangStandard::Kind)'
collect2: error: ld returned 1 exit status

I follow the steps for dev version in readme (use apt to get llvm-14 and add --with-clang-prefix when configuring), should I provide any other things?

Or is my solution for the problem in configure.ac wrong?

Hope get some instructions:)

@bondhugula
Copy link
Owner

The build error you see above comes from a version of clang headers that is incompatible with pet. Can you check 'config.log' to see which version of clang headers is being found by the configure script? clang-14, 15, 16 should all work fine.

@NicolasDerumigny
Copy link

NicolasDerumigny commented Oct 11, 2024

I encountered the same problem, and this in my case looks like a conflict between the location provided / detected for llvm-14 and the (system-wide) installation of isl, which also contains the (system-wide) llvm-18.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants