-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
[pcl] build failure #25880
Comments
Could you please provide us with |
cl: 命令行 error D8000 :C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\amd64_x86\cl.exe 中有内部编译器错误。系统将会提示你稍后向 Microsoft 发送错误报告。 请选择 Visual C++ “帮助”菜单上的“技术支持”命令,或打开技术支持帮助文件来获得详细信息 ninja: build stopped: subcommand failed. |
The log file is too large to upload |
|
vs2015,No other version is installed |
Could you please try the higher version of VS, such as VS2017 , VS2019 or VS2022? Also, if the log is too large, could you please package it and send it to us? |
Thank you for your proposal. I'll find an alternative method for the time being. As for testing with a higher version of VS, I'll talk about it later. |
Does this issue still exist? |
o shit, I meet the same question! |
I don‘t want to use PCL-AllInOne, configure VS is too boring |
@Hankyin Could you send me your complete error logs? |
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:129 (message): Call Stack (most recent call first): config-x86-windows-err.log is empty |
Please attach the right log file... |
install-x86-windows-dbg-out.log I'm so sorry, 😅 |
at the end of this log : |
I solve the problem !!! |
delete the |
Thanks for posting this issue. Please reopen this issue if this is still a problem for you. |
阿里巴巴是真滴恶心 |
Host Environment
To Reproduce
Steps to reproduce the behavior:
`./vcpkg install pcl
Failure logs
Installing 1/15 liblzma:x86-windows...
Building liblzma[core]:x86-windows...
-- Using cached xz-mirror-xz-v5.2.5.tar.gz.
-- Cleaning sources at D:/work/vcpkg/buildtrees/liblzma/src/v5.2.5-2a8bfa3c42.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source D:/work/vcpkg/downloads/xz-mirror-xz-v5.2.5.tar.gz
-- Applying patch enable-uwp-builds.patch
-- Applying patch fix_config_include.patch
-- Applying patch win_output_name.patch
-- Applying patch add_support_ios.patch
-- Applying patch build-tools.patch
-- Using source at D:/work/vcpkg/buildtrees/liblzma/src/v5.2.5-2a8bfa3c42.clean
-- Configuring x86-windows
-- Building x86-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:129 (message):
Command failed: D:/work/vcpkg/downloads/tools/cmake-3.22.2-windows/cmake-3.22.2-windows-i386/bin/cmake.exe --build . --config Debug --target install -- -v -j7
Working Directory: D:/work/vcpkg/buildtrees/liblzma/x86-windows-dbg
See logs for more information:
D:\work\vcpkg\buildtrees\liblzma\install-x86-windows-dbg-out.log
Call Stack (most recent call first):
installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake:74 (vcpkg_execute_build_process)
installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake:16 (vcpkg_cmake_build)
ports/liblzma/portfile.cmake:24 (vcpkg_cmake_install)
scripts/ports.cmake:147 (include)
error: building liblzma:x86-windows failed with: BUILD_FAILED
Please ensure you're using the latest port files with
git pull
andvcpkg update
.Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+liblzma
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[liblzma]+Build+error
Include '[liblzma] Build error' in your bug report title, the following version information in your bug description, and attach any relevant failure logs from above.
vcpkg-tool version: 2022-07-14-fb7e3b1bb3b1ca185fffe2be36b2fbc53198360f
vcpkg-scripts version: 8ff1682 2022-07-19 (8 hours ago)
You can also use the prefilled template from D:\work\vcpkg\installed\vcpkg\issue_body.md.
Additional context
Add any other context about the problem here, such as what you have already tried to resolve the issue.
The text was updated successfully, but these errors were encountered: