Christoffer Lerno
Christoffer Lerno
I'll try later, because it doesn't work yet.
How can I check that I'm using the version with the fix? I still see the LLVMExport failure if I don't import bolt-15.
It doesn't seem to have helped @sylvestre. I see my tests trying to compile both with a version from 2022-10-12 and later with one from 2022-10-13, both fails the same...
It seems to be this: ``` # Import target "llvm-bolt" for configuration "Release" set_property(TARGET llvm-bolt APPEND PROPERTY IMPORTED_CONFIGURATIONS RELEASE) set_target_properties(llvm-bolt PROPERTIES IMPORTED_LOCATION_RELEASE "${_IMPORT_PREFIX}/bin/llvm-bolt" list(APPEND _IMPORT_CHECK_TARGETS llvm-bolt ) list(APPEND _IMPORT_CHECK_FILES_FOR_llvm-bolt "${_IMPORT_PREFIX}/bin/llvm-bolt"...
Let me know when I can test again. Also, it looks like this problem found its way into 16 now.
The LLVM 15 version is still on 20221014 with the "merge-fdata" error. LLVM 16 on 20221015 is showing a new error, missing "/usr/lib/llvm-16/bin/llvm-bat-dump" instead. @sylvestre
It appears that 15.0.3 now works. But the issue in LLVM-16 remains (missing /usr/lib/llvm-16/bin/llvm-bat-dump)
Well that 15.0.3 works is related ;) Also 16 seems to work when bolt is included.
In some cases the debug printout has a TODO in it. It’s very unclear to me what’s missing (and probably other contributors would be similarly confused. I’m on a quest...
For this, it’s just debug printouts that needs to have their todos resolved.