I agree. Maybe there are no benefits, but excluding them would add more complexity.
As soon as there are (general) problems we need to reevaluate this.
@Gontier-Julien I implemented a separate LTO blacklist in https://git.harting.dev/anonfunc/ALHP.GO/commit/de3ca80aab8d1d85bbc0644d48cbc2214cb52622.
Currently on there are rust, llvm and…
I added a donation section to the FAQ, see here: https://git.harting.dev/anonfunc/ALHP.GO#donations.
Ah, rust was not removed from ALHP when it failed to build. Weird. Going to remove that shortly, then you should get the newest official version.
Well, your rustc is linking to llvm12, so no suprises there. Whats your rust package version? Should be 1:1.56.1-3 from [extra]
And also, just noticed that rust shouldn't be built with LTO:…
Could be connected to that weird llvm version that is build currently. I just blacklisted it, can you try again after downgrading llvm (and its split packages) to arch's official version?…
@titaniumtown rust seems to fail currently. Not sure if a rebuild yields new result there.
@Gontier-Julien there not currently no way to blacklist a…
But llvm-libs seem to be causing some issue at compile time, maybe should we try a rebuild with lto, and if the issue seem the same on without lto ?
I agree, we need to investigate if its caused…
That could be one of the sideffects mentioned in https://git.harting.dev/anonfunc/ALHP.GO/issues/52#issuecomment-695.
I'll requeue it and monitor if the LTO linking is OOM-killed.