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
Checks for llvm versions break on minor version update of llvm #573
Comments
This has been fixed in 5fbe042 |
Fix preprocessor conditionals that are too specific: grame-cncm/faust#573 Change ruby optdepends to ruby-rexml: grame-cncm/faust#572 git-svn-id: file:///srv/repos/svn-community/svn@919521 9fca08f4-af9d-4005-b8df-a31f2cc04f65
Fix preprocessor conditionals that are too specific: grame-cncm/faust#573 Change ruby optdepends to ruby-rexml: grame-cncm/faust#572 git-svn-id: file:///srv/repos/svn-community/svn@919521 9fca08f4-af9d-4005-b8df-a31f2cc04f65
I don't think so. The above search link still shows e.g. the remaining explicit matches against |
Build on macOS gives this kind of log: Building with macports: https://ports.macports.org/port/llvm-11/summary |
Hm, looking at our build script for llvm, I don't see anything that would suggest our distribution build deliberately choosing Given that macports applies many more patches than us, it's more likely that exposing Besides that, do you think that there's a way of doing conditional checks against the version string in the remaining locations, that do not rely on |
What do you mean? |
To do what is described in the initial ticket text and not rely on |
@sletz argh, nevermind. I just now realized what that change you mentioned actually does! 🙄 Nevermind the noise! |
Hi! When building faust 2.30.5 I used llvm 11.0.0.
After an upgrade to llvm 11.1.0 a (re)build breaks, because some files rely on overly explicit preprocessor macros: https://github.com/grame-cncm/faust/search?q=LLVM_110
llvm 11.1.0 exposes
LLVM_111
instead ofLLVM_110
and the build breaks.Maybe this can be somehow improved by relying on "greater than" comparison or by utilizing the
LLVM_VERSION
, which exposes the complete version string?The text was updated successfully, but these errors were encountered: