-
Notifications
You must be signed in to change notification settings - Fork 666
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
Building with "-D BYTECODE_RUNTIME=llvm" builds fail with llvm >=14 #581
Comments
Thank you for the report. I am working on reproducing the problem now, will let you know when I have something. |
AllocateRWX and ReleaseRWX have been replaced by allocateMappedMemory and releaseMappedMemory. It appears that there are other changes that have been made as well. I do not know at this time when upgrading our code to work with llvm 14 will be scheduled. I will keep you updated. |
Indeed, it looks like clamav doesn't support llvm > 3.6.2. |
I have tested llvm 8 - 12 with clam. Are you having issues building with those versions? EDITED: you are correct, llvm works on 0.105. |
Thanks, we'll try again when we shift to 0.105 - which will probably be a while due to the shift to rust. |
Unfortunately, I don't have an update on when this will be scheduled. |
I just wanted to ping on this one again; it's been a few months and we're now looking at LLVM 14-16 marked stable for most arches in Gentoo, with 17 on the way. I'm quite interested in enabling our users to optionally set It looks like clamav is gearing up for 1.2.0 (yay) but a quick test on Please consider this an 'I'm very interested' rather than another request for a scheduling update 😄 Edit: Can we update the issue title, too? Something more descriptive like " |
We're presently working on updating the LLVM support in the bytecode compiler and plan to address LLVM runtime support after that. But you're right, it won't make 1.2.0. |
Describe the bug
Trying to build clamav 0.104.3 on Fedora rawhide. Get:
How to reproduce the problem
The text was updated successfully, but these errors were encountered: