microsoft / vcpkg

C++ Library Manager for Windows, Linux, and MacOS
MIT License
22.81k stars 6.3k forks source link

[gmp] build failure #35098

Open For-Chance opened 10 months ago

For-Chance commented 10 months ago

Operating system

Windows 11

Compiler

No response

Steps to reproduce the behavior

I want to downgrade cgal from 5.6 to 4.14
1. Create `vcpkg.json` in root path

{
"dependencies": [
    "cgal"
  ],
  "overrides": [
    {
      "name": "cgal",
      "version": "4.14-3"
    }
  ]
}
  1. vcpkg x-update-baseline --add-initial-baseline
  2. vcpkg install --keep-going: Run it and the first time vcpkg had downloaded all packages except gmp. And then run it again, show errors as follow.

Failure logs

admin@DESKTOP-3V4ABHL MINGW64 /d/include/vcpkg (master)
$ vcpkg install --keep-going
Detecting compiler hash for triplet x64-windows...
-- Automatically setting %HTTP(S)_PROXY% environment variables to "127.0.0.1:10809".
The following packages will be built and installed:
  * gmp:x64-windows -> 6.2.1#21 -- D:\include\vcpkg\buildtrees\versioning_\versions\gmp\726604ff590362102d805e16508ae20730583101
Additional packages (*) will be modified to complete this operation.
Restored 1 package(s) from C:\Users\admin\AppData\Local\vcpkg\archives in 41.7 ms. Use --debug to see more details.
Installing 1/1 gmp:x64-windows...
error: The following files are already installed in D:/include/vcpkg/vcpkg_installed/x64-windows and are in conflict with gmp:x64-windows
Installed by mpir:x64-windows
include/gmp.h
    include/gmpxx.h

Elapsed time to handle gmp:x64-windows: 18 ms
Total install time: 18 ms

RESULTS
  gmp:x64-windows: FILE_CONFLICTS: 18 ms

Additional context

No response

dg0yt commented 9 months ago

Not a port bug. gmp and mpir can't be installed at the same time. When not installing from cache (as above), it is clearly reported: https://github.com/microsoft/vcpkg/blob/cd5e746ec203c8c3c61647e0886a8df8c1e78e41/ports/gmp/portfile.cmake#L2

Unlike MPIR, GMP is under active development.

github-actions[bot] commented 8 months ago

This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 28 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment.