You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see a lot of build failures in the issues list and I am failing to build all of the dependencies myself - are there any technological challenges that prevent packaging Souper as a .rpm or .deb? Would that package be tied to a particular git hash of LLVM tree?
The text was updated successfully, but these errors were encountered:
are there any technological challenges that prevent packaging Souper as a .rpm or .deb
That's a bit tricky as we have a out of tree patch for LLVM.
The version of LLVM itself is one of the recent release versions, which we bump about once a year.
I see a lot of build failures in the issues list and I am failing to build all of the dependencies myself - are there any technological challenges that prevent packaging Souper as a .rpm or .deb? Would that package be tied to a particular git hash of LLVM tree?
The text was updated successfully, but these errors were encountered: