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
{{ message }}
Repository navigation
Non-portable packaging of LLVMDebugInfoPDB's dependency of diaguids.lib on Windows #175
Solution to issue cannot be found in the documentation.
I checked the documentation.
Issue
Hi, I am a developer for Apache Arrow. Our windows CI has been failing recently. Error message is:
(arrow) C:\projects\arrow\cpp\build>cmake --build . --target install --config Release || exit /B
ninja: error: 'C:/Program Files (x86)/Microsoft Visual Studio/2019/Enterprise/DIA SDK/lib/amd64/diaguids.lib', needed by 'release/gandiva.dll', missing and no known rule to make it
Our ci environment has VS2019 community version but ninja is looking for the enterprise version.
After some digging I found out there's a portability issue with Conda's packaging of LLVM on windows.
changed the title [-]Non-portable packaging of llvmdev target LLVMDebugInfoPDB dependency[/-][+]Non-portable packaging of LLVMDebugInfoPDB dependency on diaguids.lib on Windows[/+]on Sep 24, 2022
changed the title [-]Non-portable packaging of LLVMDebugInfoPDB dependency on diaguids.lib on Windows[/-][+]Non-portable packaging of LLVMDebugInfoPDB's dependency of diaguids.lib on Windows[/+]on Sep 24, 2022
This should be fixed now on LLVM 14, 15 & 161. The builds should be available in a couple hours.
Footnotes
16 will take a bit longer to become fully available because we're still rolling out the remaining components of 16.0.4 before updating the activation ↩
Activity
[-]Non-portable packaging of llvmdev target LLVMDebugInfoPDB dependency[/-][+]Non-portable packaging of LLVMDebugInfoPDB dependency on diaguids.lib on Windows[/+][-]Non-portable packaging of LLVMDebugInfoPDB dependency on diaguids.lib on Windows[/-][+]Non-portable packaging of LLVMDebugInfoPDB's dependency of diaguids.lib on Windows[/+]h-vetinari commentedon May 17, 2023
This should be fixed now on LLVM 14, 15 & 161. The builds should be available in a couple hours.
Footnotes
16 will take a bit longer to become fully available because we're still rolling out the remaining components of 16.0.4 before updating the activation ↩
Run CI with LLVM 15 on Windows