Tom,
you can drop the clcache dependency if that helps. Otherwise try to
create a conda env from scratch (if you didn't do that)
Even
Le 11/07/2025 à 02:31, Tom Moore via gdal-dev a écrit :
Newbie here. As the title says I am trying to set up a build environment.
I was trying to follow the instructions from the website:
https://gdal.org/en/stable/development/dev_environment.html
I got to the step to install the compiler and got an error about
conflicts and the process stopped. Does anyone have a clue about what
is going wrong here?? Output follows:
===== start of output
(gdal) C:\Users\tmoore> conda install --yes -c conda-forge compilers
clcache
Channels:
- conda-forge
- defaults
Platform: win-64
Collecting package metadata (repodata.json): done
Solving environment: failed
LibMambaUnsatisfiableError: Encountered problems while solving:
- nothing provides vc 10.* needed by python-3.4.5-0
Could not solve for environment specs
The following packages are incompatible
├─ clcache =* * is installable with the potential options
│ ├─ clcache 4.2.0 would require
│ │ └─ python >=3.10,<3.11.0a0 *, which can be installed;
│ ├─ clcache [4.1.0|4.2.0] would require
│ │ └─ python >=3.8,<3.9.0a0 *, which can be installed;
│ ├─ clcache [4.1.0|4.2.0] would require
│ │ └─ python >=3.9,<3.10.0a0 *, which can be installed;
│ ├─ clcache 3.3.0 would require
│ │ └─ python =3.4 * but there are no viable options
│ │ ├─ python 3.4.5 would require
│ │ │ └─ vc =10 *, which does not exist (perhaps a missing channel);
│ │ └─ python 3.4.5 would require
│ │ └─ vs2010_runtime =* *, which does not exist (perhaps a
missing channel);
│ ├─ clcache [3.3.0|4.0.0|4.1.0] would require
│ │ └─ python [=3.5 *|>=3.5,<3.6.0a0 *], which can be installed;
│ ├─ clcache [4.0.0|4.1.0] would require
│ │ └─ python =3.6 *, which can be installed;
│ ├─ clcache [4.1.0|4.2.0] would require
│ │ └─ python >=3.6,<3.7.0a0 *, which can be installed;
│ └─ clcache 4.1.0 would require
│ └─ python >=3.7,<3.8.0a0 *, which can be installed;
└─ pin on python 3.13.* =* * is not installable because it requires
└─ python =3.13 *, which conflicts with any installable versions
previously reported.
Pins seem to be involved in the conflict. Currently pinned specs:
- python=3.13
==== end of output
Thanks, Tom
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
--
http://www.spatialys.com
My software is free, but my time generally not.
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
