Skip to content
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

cftime does not compile from wheel on Windows Server 2019 #222

Closed
cphyc opened this issue Jan 18, 2021 · 2 comments
Closed

cftime does not compile from wheel on Windows Server 2019 #222

cphyc opened this issue Jan 18, 2021 · 2 comments

Comments

@cphyc
Copy link

cphyc commented Jan 18, 2021

cftime is an upstream dependency of the yt project (http://yt-project.org). Since the release of cftime 1.3.1, our testing infrastructure is however unable to build cftime (from pip). Here is the backlog:


  creating build\temp.win-amd64-3.9\Release
  creating build\temp.win-amd64-3.9\Release\Users
  creating build\temp.win-amd64-3.9\Release\Users\runneradmin
  creating build\temp.win-amd64-3.9\Release\Users\runneradmin\AppData
Successfully built coverage f90nml fastcache MiniballCpp nose-timer bottleneck fast-histogram mpmath nose-exclude
Failed to build cftime
  creating build\temp.win-amd64-3.9\Release\Users\runneradmin\AppData\Local
  creating build\temp.win-amd64-3.9\Release\Users\runneradmin\AppData\Local\Temp
  creating build\temp.win-amd64-3.9\Release\Users\runneradmin\AppData\Local\Temp\pip-install-rrekve4q
  creating build\temp.win-amd64-3.9\Release\Users\runneradmin\AppData\Local\Temp\pip-install-rrekve4q\cftime_364646372aeb4369a4492d8637b98d78
  creating build\temp.win-amd64-3.9\Release\Users\runneradmin\AppData\Local\Temp\pip-install-rrekve4q\cftime_364646372aeb4369a4492d8637b98d78\src
  creating build\temp.win-amd64-3.9\Release\Users\runneradmin\AppData\Local\Temp\pip-install-rrekve4q\cftime_364646372aeb4369a4492d8637b98d78\src\cftime
  C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.28.29333\bin\HostX86\x64\cl.exe /c /nologo /Ox /W3 /GL /DNDEBUG /MD -IC:\Users\runneradmin\AppData\Local\Temp\pip-build-env-c35306xl\overlay\Lib\site-packages\numpy\core\include -IC:\Miniconda\include -IC:\Miniconda\include -IC:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.28.29333\ATLMFC\include -IC:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.28.29333\include -IC:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\include\um -IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\ucrt -IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\shared -IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\um -IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\winrt -IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\cppwinrt /TcC:\Users\runneradmin\AppData\Local\Temp\pip-install-rrekve4q\cftime_364646372aeb4369a4492d8637b98d78\src\cftime\_cftime.c /Fobuild\temp.win-amd64-3.9\Release\Users\runneradmin\AppData\Local\Temp\pip-install-rrekve4q\cftime_364646372aeb4369a4492d8637b98d78\src\cftime\_cftime.obj
  _cftime.c
  C:\Users\runneradmin\AppData\Local\Temp\pip-build-env-c35306xl\overlay\Lib\site-packages\numpy\core\include\numpy\npy_1_7_deprecated_api.h(14) : Warning Msg: Using deprecated NumPy API, disable it with #define NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION
  C:\Users\runneradmin\AppData\Local\Temp\pip-install-rrekve4q\cftime_364646372aeb4369a4492d8637b98d78\src\cftime\_cftime.c(16826): warning C4996: '_PyUnicode_get_wstr_length': deprecated in 3.3
  C:\Users\runneradmin\AppData\Local\Temp\pip-install-rrekve4q\cftime_364646372aeb4369a4492d8637b98d78\src\cftime\_cftime.c(17125): warning C4996: '_PyUnicode_get_wstr_length': deprecated in 3.3
  C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.28.29333\bin\HostX86\x64\link.exe /nologo /INCREMENTAL:NO /LTCG /DLL /MANIFEST:EMBED,ID=2 /MANIFESTUAC:NO /LIBPATH:C:\Miniconda\libs /LIBPATH:C:\Miniconda\PCbuild\amd64 /LIBPATH:C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.28.29333\ATLMFC\lib\x64 /LIBPATH:C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.28.29333\lib\x64 /LIBPATH:C:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\lib\um\x64 /LIBPATH:C:\Program Files (x86)\Windows Kits\10\lib\10.0.19041.0\ucrt\x64 /LIBPATH:C:\Program Files (x86)\Windows Kits\10\lib\10.0.19041.0\um\x64 /EXPORT:PyInit__cftime build\temp.win-amd64-3.9\Release\Users\runneradmin\AppData\Local\Temp\pip-install-rrekve4q\cftime_364646372aeb4369a4492d8637b98d78\src\cftime\_cftime.obj /OUT:build\lib.win-amd64-3.9\cftime\_cftime.cp39-win_amd64.pyd /IMPLIB:build\temp.win-amd64-3.9\Release\Users\runneradmin\AppData\Local\Temp\pip-install-rrekve4q\cftime_364646372aeb4369a4492d8637b98d78\src\cftime\_cftime.cp39-win_amd64.lib
  LINK : fatal error LNK1104: cannot open file 'build\temp.win-amd64-3.9\Release\Users\runneradmin\AppData\Local\Temp\pip-install-rrekve4q\cftime_364646372aeb4369a4492d8637b98d78\src\cftime\_cftime.cp39-win_amd64.exp'
  error: command 'C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Enterprise\\VC\\Tools\\MSVC\\14.28.29333\\bin\\HostX86\\x64\\link.exe' failed with exit code 1104
  ----------------------------------------
  ERROR: Failed building wheel for cftime
ERROR: Could not build wheels for cftime which use PEP 517 and cannot be installed directly

Here is the detail of our environment:

  • cftime 1.3.1
  • OS: Windows (Microsoft Windows Server 2019)
  • Python 3.8 and 3.9 (haven't tested other versions).
  • Using conda version : 4.9.2 (used to setup the env. not, to install cftime).

Note that cftime 1.3.0 works great.

Extra notes

Here is a link to a failing build https://github.com/yt-project/yt/pull/2978/checks?check_run_id=1720969048.

@jswhit
Copy link
Collaborator

jswhit commented Jan 18, 2021

That's because there were no windows wheels uploaded to pypi yet for 1.3.1, so pip tried to build from source. The windows wheels are up now, so please try again.

@cphyc
Copy link
Author

cphyc commented Jan 18, 2021

I can confirm the issue is now fixed, closing this issue. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants